about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* sandbox: no way to run arbitrary Lua code stringsKartik K. Agaram2022-02-021-96/+0
|
* include keys typed into audit logKartik K. Agaram2022-02-013-0/+18
| | | | | This will help people cross-correlate when the app performs specific calls.
* new potential threat vectorKartik K. Agaram2022-02-011-0/+3
|
* file permissions: decide based on calling functionKartik K. Agaram2022-02-014-15/+30
|
* copy realpath() from FreeBSD repoKartik K. Agaram2022-01-302-1/+245
| | | | | To sandbox apps robustly, we're going to need to always work with canonical absolute paths.
* try to get by with one feature macroKartik K. Agaram2022-01-295-11/+1
| | | | | | | | | | | | | | | | | I fucking hate feature macros. Egregious discharge of our division-of-labor-obsessed society. People should be able to introduce names. People should be able to give up names to lower levels of abstraction when they encounter conflicts. Feature macros seem to exist[1] to support more than two levels of abstraction. You try to build, one of your libraries fails to build because of a conflict between it and one level down. You don't want to modify this library. Just fucking https://catern.com/change_code.html already. But no, I have to litter my code with feature macros even though I just want the abstraction the original library provides. [1] https://man7.org/linux/man-pages/man7/feature_test_macros.7.html https://lwn.net/Articles/590381
* new library: luafilesystem (lfs)Kartik K. Agaram2022-01-297-1/+1425
| | | | | | https://github.com/keplerproject/luafilesystem The new commander.tlv app demonstrates it working.
* fixup! redo lua vs proseKartik K. Agaram2022-01-291-15/+17
| | | | Forgot to include some hunks.
* more precise dependenciesKartik K. Agaram2022-01-291-2/+2
|
* incomplete lisp interpreter appKartik K. Agaram2022-01-272-0/+907
| | | | | I'm not sure what I'm doing here just yet. This is just an experiment of the editing experience. The .tlv app doesn't actually do anything yet.
* 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
|