Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | sandbox: no way to run arbitrary Lua code strings | Kartik K. Agaram | 2022-02-02 | 1 | -96/+0 |
| | |||||
* | include keys typed into audit log | Kartik K. Agaram | 2022-02-01 | 3 | -0/+18 |
| | | | | | This will help people cross-correlate when the app performs specific calls. | ||||
* | file permissions: decide based on calling function | Kartik K. Agaram | 2022-02-01 | 4 | -15/+30 |
| | |||||
* | copy realpath() from FreeBSD repo | Kartik K. Agaram | 2022-01-30 | 2 | -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 macro | Kartik K. Agaram | 2022-01-29 | 5 | -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. Agaram | 2022-01-29 | 5 | -1/+1224 |
| | | | | | | https://github.com/keplerproject/luafilesystem The new commander.tlv app demonstrates it working. | ||||
* | fixup! redo lua vs prose | Kartik K. Agaram | 2022-01-29 | 1 | -15/+17 |
| | | | | Forgot to include some hunks. | ||||
* | more precise dependencies | Kartik K. Agaram | 2022-01-29 | 1 | -2/+2 |
| | |||||
* | bugfix: editor was no longer saving anything | Kartik K. Agaram | 2022-01-27 | 1 | -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 prose | Kartik K. Agaram | 2022-01-26 | 2 | -13/+19 |
| | | | | | Previously we weren't dynamically selecting how to highlight a buffer after navigating with ctrl-g. That should work now. | ||||
* | indent | Kartik K. Agaram | 2022-01-26 | 1 | -8/+8 |
| | |||||
* | get Teliva working on FreeBSD | Kartik K. Agaram | 2022-01-26 | 1 | -1/+3 |
| | |||||
* | rename the custom big picture view to doc:main | Kartik K. Agaram | 2022-01-25 | 1 | -1/+2 |
| | |||||
* | override big picture view with doc:bp if it exists | Kartik K. Agaram | 2022-01-25 | 1 | -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 prose | Kartik K. Agaram | 2022-01-25 | 1 | -2/+2 |
| | |||||
* | highlight [[wikiwords]] in prose | Kartik K. Agaram | 2022-01-25 | 1 | -24/+71 |
| | | | | | These are just hints that there's something worth jumping to. The jumping still happens using ctrl-g. | ||||
* | disable Lua colors in prose | Kartik K. Agaram | 2022-01-25 | 2 | -10/+54 |
| | |||||
* | rename | Kartik K. Agaram | 2022-01-25 | 2 | -6/+6 |
| | |||||
* | new section in big picture: prose (non-code) | Kartik K. Agaram | 2022-01-25 | 1 | -4/+33 |
| | | | | I've always found "Documentation" too pretentious. | ||||
* | optimization: stop saving identical definitions | Kartik K. Agaram | 2022-01-25 | 1 | -0/+7 |
| | | | | This is long overdue. | ||||
* | save doc: buffers to .tlv images | Kartik K. Agaram | 2022-01-25 | 2 | -2/+17 |
| | |||||
* | delete a redundant function prototype | Kartik K. Agaram | 2022-01-25 | 1 | -2/+1 |
| | |||||
* | rename a function | Kartik K. Agaram | 2022-01-25 | 3 | -6/+6 |
| | |||||
* | start supporting non-code "buffers" | Kartik K. Agaram | 2022-01-25 | 1 | -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. | ||||
* | work around a bug in NetBSD libcurses | Kartik K. Agaram | 2022-01-24 | 1 | -0/+1 |
| | | | | http://gnats.netbsd.org/56664 reported. | ||||
* | get Teliva running on NetBSD | Kartik K. Agaram | 2022-01-24 | 7 | -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 code | Kartik K. Agaram | 2022-01-24 | 3 | -62/+0 |
| | | | | | I'm kinda sorta able to get lcurses running on NetBSD 9.2 without this particular hack. | ||||
* | more generic build target in luasocket | Kartik K. Agaram | 2022-01-24 | 2 | -14/+14 |
| | |||||
* | clarify generic 'bsd' build target | Kartik K. Agaram | 2022-01-24 | 1 | -7/+13 |
| | | | | We still only have OpenBSD working. | ||||
* | file permissions: clear stale errors | Kartik K. Agaram | 2022-01-16 | 1 | -0/+1 |
| | |||||
* | editing apps: clean up some stale prints | Kartik K. Agaram | 2022-01-16 | 1 | -0/+6 |
| | |||||
* | file access policy: support editing with >10 lines | Kartik K. Agaram | 2022-01-16 | 1 | -3/+5 |
| | |||||
* | kilo: cleaner go menu | Kartik K. Agaram | 2022-01-11 | 1 | -0/+2 |
| | |||||
* | some heuristic guidance on permissions screen | Kartik K. Agaram | 2022-01-04 | 1 | -2/+59 |
| | |||||
* | try running permissions advice after editing | Kartik K. Agaram | 2022-01-04 | 1 | -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 message | Kartik K. Agaram | 2022-01-04 | 1 | -1/+6 |
| | |||||
* | reorg | Kartik K. Agaram | 2022-01-04 | 1 | -17/+17 |
| | |||||
* | feels more consistent to exit editor with ctrl-x | Kartik K. Agaram | 2022-01-04 | 1 | -3/+3 |
| | |||||
* | extract function | Kartik K. Agaram | 2022-01-04 | 1 | -23/+14 |
| | |||||
* | load permissions properly in a third place | Kartik K. Agaram | 2022-01-04 | 1 | -2/+9 |
| | |||||
* | when editing a function, show its callers | Kartik K. Agaram | 2022-01-03 | 4 | -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 functions | Kartik K. Agaram | 2022-01-03 | 3 | -2/+55 |
| | | | | | I think this is significantly slowing things down. Perhaps we should sample or something. | ||||
* | comment | Kartik K. Agaram | 2022-01-03 | 1 | -1/+1 |
| | |||||
* | rename | Kartik K. Agaram | 2022-01-03 | 1 | -2/+2 |
| | |||||
* | extract a function | Kartik K. Agaram | 2022-01-03 | 3 | -21/+24 |
| | |||||
* | events view: jump to a function | Kartik K. Agaram | 2022-01-03 | 1 | -7/+27 |
| | |||||
* | rendering improvement | Kartik K. Agaram | 2022-01-02 | 1 | -3/+2 |
| | |||||
* | error handling when editing file permissions | Kartik K. Agaram | 2022-01-02 | 1 | -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 newline | Kartik K. Agaram | 2022-01-02 | 1 | -3/+3 |
| | | | | I believe kilo kinda naturally enforces that. We'll see. | ||||
* | instrument some obvious syscalls | Kartik K. Agaram | 2022-01-02 | 3 | -1/+31 |
| |