about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* bugfix: editor was no longer saving anythingKartik K. Agaram2022-01-271-4/+2
| | | | | | I made the changes reverted here out of a mistaken sense that big-picture edits would interfere with Teliva's memory of what is currently being edited (teliva_editor_state).
* redo lua vs proseKartik K. Agaram2022-01-262-13/+19
| | | | | Previously we weren't dynamically selecting how to highlight a buffer after navigating with ctrl-g. That should work now.
* indentKartik K. Agaram2022-01-261-8/+8
|
* get Teliva working on FreeBSDKartik K. Agaram2022-01-262-3/+6
|
* rename the custom big picture view to doc:mainKartik K. Agaram2022-01-251-1/+2
|
* override big picture view with doc:bp if it existsKartik K. Agaram2022-01-251-2/+18
| | | | | | | | | | | Going to big picture from doc:bp still goes to the default auto-generated big picture view. While doc:bp provides some programmability, it's also far klunkier than the default view. Rendering is worse, and it's always in edit mode because I'm trying to avoid complicating the UX with a notion of rendered markup. That means cursor movement is less convenient. It's also easy to accidentally edit the big-picture view.
* better default word at cursor for proseKartik K. Agaram2022-01-251-2/+2
|
* highlight [[wikiwords]] in proseKartik K. Agaram2022-01-251-24/+71
| | | | | These are just hints that there's something worth jumping to. The jumping still happens using ctrl-g.
* disable Lua colors in proseKartik K. Agaram2022-01-252-10/+54
|
* renameKartik K. Agaram2022-01-252-6/+6
|
* new section in big picture: prose (non-code)Kartik K. Agaram2022-01-251-4/+33
| | | | I've always found "Documentation" too pretentious.
* optimization: stop saving identical definitionsKartik K. Agaram2022-01-251-0/+7
| | | | This is long overdue.
* save doc: buffers to .tlv imagesKartik K. Agaram2022-01-252-2/+17
|
* delete a redundant function prototypeKartik K. Agaram2022-01-251-2/+1
|
* rename a functionKartik K. Agaram2022-01-253-6/+6
|
* start supporting non-code "buffers"Kartik K. Agaram2022-01-251-0/+6
| | | | | First step: when a "definition" starts with "doc:" it's not a definition, just a buffer. Stop trying to interpret it as Lua.
* documentation for NetBSDKartik K. Agaram2022-01-241-3/+6
|
* work around a bug in NetBSD libcursesKartik K. Agaram2022-01-241-0/+1
| | | | http://gnats.netbsd.org/56664 reported.
* get Teliva running on NetBSDKartik K. Agaram2022-01-247-1/+25
| | | | | | | | NetBSD still uses curses by default. One _could_ install ncurses, but I don't have access to a NetBSD box with permissions to install ncurses, so I'm experimenting to see how far we can get with just curses. So far most of the apps seem to work, with the exception of one bug that I'll commit next.
* delete some dead codeKartik K. Agaram2022-01-243-62/+0
| | | | | I'm kinda sorta able to get lcurses running on NetBSD 9.2 without this particular hack.
* known issue on OpenBSDKartik K. Agaram2022-01-241-0/+3
|
* more generic build target in luasocketKartik K. Agaram2022-01-242-14/+14
|
* clarify generic 'bsd' build targetKartik K. Agaram2022-01-243-9/+15
| | | | We still only have OpenBSD working.
* gemini: demo of context-sensitive menuKartik K. Agaram2022-01-181-1/+8
| | | | | | | Basic procedure: - save/restore `menu` around call of a function (directly or indirectly called by `update`) that encapsulates some state change - override `menu` inside the function to correspond to its update loop
* file permissions: clear stale errorsKartik K. Agaram2022-01-161-0/+1
|
* editing apps: clean up some stale printsKartik K. Agaram2022-01-161-0/+6
|
* file access policy: support editing with >10 linesKartik K. Agaram2022-01-161-3/+5
|
* clearer first sentenceKartik K. Agaram2022-01-141-3/+4
|
* enumerate mirrorsKartik K. Agaram2022-01-141-0/+14
|
* kilo: cleaner go menuKartik K. Agaram2022-01-111-0/+2
|
* some heuristic guidance on permissions screenKartik K. Agaram2022-01-041-2/+59
|
* try running permissions advice after editingKartik K. Agaram2022-01-041-3/+21
| | | | | This implies it must be side-effect free. We still need to figure out how to convey that to the computer owner.
* slightly better error messageKartik K. Agaram2022-01-041-1/+6
|
* reorgKartik K. Agaram2022-01-041-17/+17
|
* feels more consistent to exit editor with ctrl-xKartik K. Agaram2022-01-041-3/+3
|
* extract functionKartik K. Agaram2022-01-041-23/+14
|
* load permissions properly in a third placeKartik K. Agaram2022-01-041-2/+9
|
* when editing a function, show its callersKartik K. Agaram2022-01-034-10/+63
| | | | | | No way to select between them. That complicates the UI too much when we do so much with the cursor. But it's still useful to suggest things to type in after ctrl-g.
* start saving callers of functionsKartik K. Agaram2022-01-033-2/+55
| | | | | I think this is significantly slowing things down. Perhaps we should sample or something.
* commentKartik K. Agaram2022-01-031-1/+1
|
* renameKartik K. Agaram2022-01-031-2/+2
|
* extract a functionKartik K. Agaram2022-01-033-21/+24
|
* events view: jump to a functionKartik K. Agaram2022-01-031-7/+27
|
* toot-toot: gracefully handle lack of permissionsKartik K. Agaram2022-01-031-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | This opens up a whole new can of worms: Teliva's ability to show clear error messages hinges on apps having decent error handling. I suppose that's ok. A new app someone downloads that throws out strange error messages and puts them in the equivalent of the console doesn't exactly engender trust. It's reasonable to treat poor error handling as breakage. Here's my running list of open questions from working on the permissions screen so far: - how to teach people to care about the difference between: - permissions known to be unsafe - permissions unknown to be safe - how to show syntax errors in the permissions screen - how to detect syntax errors in the permissions screen (lots of stuff only shows up when running) - how to deal with apps with poor error handling (this commit; punt for now) - how to engender skepticism in people towards what apps tell them ("oh, just go into the permissions screen and type ___ to fix this error") - how to help people judge the quality of their permissions (mode == 'r' vs mode ~= 'w')
* rendering improvementKartik K. Agaram2022-01-021-3/+2
|
* error handling when editing file permissionsKartik K. Agaram2022-01-021-1/+21
| | | | | | | Still highly non-ideal. Lua is a dynamic language, and has low ability to detect syntax errors within functions. Perhaps I should run a test call after every edit.
* bugfix: policies must end in newlineKartik K. Agaram2022-01-021-3/+3
| | | | I believe kilo kinda naturally enforces that. We'll see.
* instrument some obvious syscallsKartik K. Agaram2022-01-023-1/+31
|
* indentKartik K. Agaram2022-01-021-6/+6
|
* start on a view of audit eventsKartik K. Agaram2022-01-023-2/+73
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-15 14:43:27 +0000