Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | show app blurb in screenshot | Kartik K. Agaram | 2022-02-17 | 1 | -0/+0 |
| | |||||
* | 'doc:blurb': a place to briefly describe an app | Kartik K. Agaram | 2022-02-17 | 9 | -1/+79 |
| | | | | | | This is for what the app does, as opposed to 'doc:main', which is also intended to include commentary about the internal organization of the app. | ||||
* | fix a conflicting keyboard shortcut | Kartik K. Agaram | 2022-02-17 | 1 | -2/+2 |
| | |||||
* | disable non-portable ASan flags | Kartik K. Agaram | 2022-02-16 | 1 | -2/+2 |
| | |||||
* | fix chesstv.tlv after we introduced sandboxing | Kartik K. Agaram | 2022-02-12 | 1 | -0/+23 |
| | |||||
* | zet.tlv: new shortcuts, mostly for the editor | Kartik K. Agaram | 2022-02-12 | 1 | -0/+3447 |
| | |||||
* | zet.tlv: some more editor shortcuts | Kartik K. Agaram | 2022-02-12 | 2 | -2/+438 |
| | |||||
* | stop aborting if audit log fills up | Kartik K. Agaram | 2022-02-12 | 1 | -10/+32 |
| | | | | | | | | | | | | When I started logging getch() events (which are just to help the reader orient on the log), this suddenly became more urgent. Now the log is larger, and it's also a circular buffer that rolls back to the start when it fills up. The next failure mode will be if we see the buffer filled up with just getch() calls, reducing visibility over real file and network operations. In which case we'll need to start coalescing getch() events. | ||||
* | zet.tlv: yet another bugfix | Kartik K. Agaram | 2022-02-11 | 1 | -0/+141 |
| | | | | Need for tests growing more acute.. | ||||
* | fix build on Mac OS | Kartik K. Agaram | 2022-02-10 | 2 | -0/+3 |
| | |||||
* | zet.tlv: fix a couple more bugs | Kartik K. Agaram | 2022-02-10 | 1 | -0/+81 |
| | | | | This snapshot was demoed at https://archive.org/details/akkartik-teliva-2022-02-10 | ||||
* | zet.tlv: cross-links | Kartik K. Agaram | 2022-02-10 | 1 | -0/+820 |
| | | | | | | | | | | | | | | We also made render dynamic, showing zettels in the first place it encounters them in depth-first order. Open question: how to show a collapsed outline view with the data model I'm experimenting with. Not even clear 'outline' has meaning in the presence of cross-links. Outliners privilege one view of the network. Zettelkasten also does so; changing child/sibling relationships is a lot of work. However, reading between the links it seems to try to provide an escape hatch for rethinking connections using cross-links. I'm trying to lean into that -- at the cost of providing outlines. We'll see if this is a good trade-off. | ||||
* | hacky support for caller main in file permissions | Kartik K. Agaram | 2022-02-10 | 1 | -0/+2 |
| | |||||
* | fixup! clean up top-level Makefile targets | Kartik K. Agaram | 2022-02-10 | 1 | -0/+1 |
| | |||||
* | allow Teliva to show its sandboxing message | Kartik K. Agaram | 2022-02-10 | 1 | -2/+4 |
| | |||||
* | zet.tlv: refine the initial UX some more | Kartik K. Agaram | 2022-02-10 | 1 | -0/+47 |
| | | | | | | | | | | | | | | | | | | | | Conundrum: I want the app to provide some sample data for people to interact with. However, I also want them to be able to delete it to make it their own. BUT I'm not yet convinced the app should allow deletion in general. Besides, deleting stuff robustly and reliably is a whole other level of programming. Solution: Make people edit the app to clear the initial sample zettels. This has the "beneficial" side-effect of getting them editing apps on Teliva. | ||||
* | zet.tlv: copy in sample zettels | Kartik K. Agaram | 2022-02-10 | 1 | -4/+4 |
| | |||||
* | zet.tlv: saving/loading to/from disk | Kartik K. Agaram | 2022-02-10 | 1 | -0/+76 |
| | |||||
* | zet.tlv | Kartik K. Agaram | 2022-02-10 | 1 | -0/+131 |
| | |||||
* | clean up top-level Makefile targets | Kartik K. Agaram | 2022-02-10 | 1 | -2/+2 |
| | |||||
* | zet.tlv: resizing zettel card sizes | Kartik K. Agaram | 2022-02-10 | 1 | -0/+124 |
| | |||||
* | zet.tlv: creating new zettels | Kartik K. Agaram | 2022-02-09 | 1 | -0/+211 |
| | |||||
* | zet.tlv: bugfixes to editor cursor handling | Kartik K. Agaram | 2022-02-09 | 1 | -5/+4 |
| | |||||
* | . | Kartik K. Agaram | 2022-02-09 | 1 | -2/+2 |
| | |||||
* | flesh out sandboxing in Readme a tad | Kartik K. Agaram | 2022-02-09 | 1 | -3/+4 |
| | |||||
* | update keyboard shortcuts in screenshots and docs | Kartik K. Agaram | 2022-02-09 | 3 | -3/+3 |
| | |||||
* | standardize key order in .tlv files | Kartik K. Agaram | 2022-02-09 | 5 | -40/+57 |
| | | | | This will eliminate some spurious git diffs I keep having to clean up. | ||||
* | zet.tlv: simpler UI, simpler editor | Kartik K. Agaram | 2022-02-09 | 1 | -0/+184 |
| | |||||
* | bugfix in rendering non-top zettels | Kartik K. Agaram | 2022-02-08 | 1 | -1/+1 |
| | |||||
* | Lua gotcha: iterating over strings yields strings | Kartik K. Agaram | 2022-02-08 | 2 | -4/+4 |
| | |||||
* | zet.tlv: expand editor to accomodate more text | Kartik K. Agaram | 2022-02-08 | 1 | -7/+12 |
| | | | | | Still won't show up in view mode for now. Soon we'll be able to adjust zettel dimensions. | ||||
* | typo | Kartik K. Agaram | 2022-02-08 | 1 | -1/+1 |
| | |||||
* | zet.tlv: editing a single zettel | Kartik K. Agaram | 2022-02-08 | 1 | -7/+307 |
| | |||||
* | gemini.tlv: consistent menu | Kartik K. Agaram | 2022-02-08 | 1 | -2/+2 |
| | |||||
* | zet.tlv: clean up history | Kartik K. Agaram | 2022-02-07 | 1 | -2590/+17 |
| | |||||
* | move most Teliva menus to the right | Kartik K. Agaram | 2022-02-07 | 2 | -6/+8 |
| | | | | | | | | | | The problem I'm running into is that apps might want to perform their own editing. So I can't take up prime estate like the ctrl-e hotkey or a menu name of 'edit'. I'm still prioritizing rendering Teliva's edit and permissions menu. If the window is too narrow the app's settings will be overwritten and Teliva's hotkeys will be preferentially displayed. Seems safer. | ||||
* | more Readme polish | Kartik K. Agaram | 2022-02-07 | 1 | -5/+8 |
| | |||||
* | remove dropped functions from docs | Kartik K. Agaram | 2022-02-07 | 3 | -731/+5 |
| | |||||
* | question raised during FOSDEM '22 | Kartik K. Agaram | 2022-02-07 | 1 | -0/+2 |
| | | | | https://fosdem.org/2022/schedule/event/lastmilesandboxing | ||||
* | lisp.tlv: clean up history | Kartik K. Agaram | 2022-02-07 | 1 | -309/+26 |
| | | | | Also a minor edit in doc:main. | ||||
* | some more dead code | Kartik K. Agaram | 2022-02-06 | 1 | -23/+0 |
| | |||||
* | in fact, loadlib.c is all dead code now | Kartik K. Agaram | 2022-02-06 | 2 | -299/+1 |
| | | | | Now we can be sure apps can't call `require`. | ||||
* | now all our supported platforms are POSIX | Kartik K. Agaram | 2022-02-06 | 2 | -14/+5 |
| | |||||
* | drop all support for loading dynamic libraries | Kartik K. Agaram | 2022-02-06 | 2 | -338/+7 |
| | |||||
* | drop module 'package' | Kartik K. Agaram | 2022-02-06 | 4 | -49/+0 |
| | | | | | | | Just like with `require`, we don't we don't know how to sandbox it. (Though we still have `require` because standard libraries outside apps need it. I need to make sure apps can't invoke `require`..) | ||||
* | drop some more untested platforms | Kartik K. Agaram | 2022-02-06 | 1 | -16/+1 |
| | |||||
* | drop USE_LINUX and similar defines | Kartik K. Agaram | 2022-02-06 | 2 | -15/+4 |
| | | | | | How many levels of macros do we need. Also stop lying that we're using Linux in BSD. | ||||
* | drop MinGW | Kartik K. Agaram | 2022-02-06 | 1 | -6/+1 |
| | | | | | | | | I've never tested with it, and it is likely broken after all my changes to base Lua 5.1. Might as well be transparent about that. If you care about this platform, please let me know: http://akkartik.name/contact | ||||
* | unused #define | Kartik K. Agaram | 2022-02-06 | 1 | -1/+0 |
| | |||||
* | more thoughts on sandboxing | Kartik K. Agaram | 2022-02-05 | 1 | -0/+8 |
| |