| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | 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 | 3 | -9/+15 | |
| | | | | | We still only have OpenBSD working. | |||||
| * | gemini: demo of context-sensitive menu | Kartik K. Agaram | 2022-01-18 | 1 | -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 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 | |
| | | ||||||
| * | clearer first sentence | Kartik K. Agaram | 2022-01-14 | 1 | -3/+4 | |
| | | ||||||
| * | enumerate mirrors | Kartik K. Agaram | 2022-01-14 | 1 | -0/+14 | |
| | | ||||||
| * | 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 | |
| | | ||||||
| * | toot-toot: gracefully handle lack of permissions | Kartik K. Agaram | 2022-01-03 | 1 | -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 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 | |
| | | ||||||
| * | indent | Kartik K. Agaram | 2022-01-02 | 1 | -6/+6 | |
| | | ||||||
| * | start on a view of audit events | Kartik K. Agaram | 2022-01-02 | 3 | -2/+73 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-01-02 | 1 | -3/+0 | |
| | | ||||||
| * | editing file permissions | Kartik K. Agaram | 2022-01-02 | 2 | -42/+76 | |
| | | ||||||
| * | make some space for callers of a function | Kartik K. Agaram | 2022-01-02 | 1 | -13/+26 | |
| | | ||||||
| * | start parameterizing viewport for editor | Kartik K. Agaram | 2022-01-02 | 1 | -8/+18 | |
| | | ||||||
| * | drop os.getenv | Kartik K. Agaram | 2022-01-02 | 1 | -7/+1 | |
| | | ||||||
| * | editable file permissions | Kartik K. Agaram | 2022-01-02 | 4 | -51/+192 | |
| | | | | | | | | | | | | | | | | | | | | | | Extremely cruddy implementation: - I'm still unclear on how to represent the advice function: - How to handle errors when loading user configuration? Currently I refuse to start. - Whole function? More errors to handle in header and so on. What if the function is renamed? - Just body? Needs more structured editing support. - Lots of duplication, particularly between the permissions in the menu and the permissions screen. I don't know how to show the hostname at the time of connect() or bind(), so networking is going to remain a boolean for now. It's also unclear what effective constraints we can impose on what gets discussed with a specific hostname. Everything outside the computer is out of one's control. One trick I learned is for consistently grabbing ASan logs on abort: It's always safe to redirect stderr with ncurses! | |||||
| * | fork a new editor widget for non-code | Kartik K. Agaram | 2022-01-02 | 2 | -2/+49 | |
| | | ||||||
| * | better follow kilo's naming conventions | Kartik K. Agaram | 2022-01-02 | 2 | -6/+6 | |
| | | ||||||
| * | start peeling out an editor for non-code | Kartik K. Agaram | 2022-01-02 | 1 | -14/+21 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-01-02 | 2 | -1/+3 | |
| | | ||||||
| * | copy tweak | Kartik K. Agaram | 2022-01-02 | 1 | -3/+4 | |
| | | ||||||
| * | rename | Kartik K. Agaram | 2022-01-02 | 4 | -31/+31 | |
| | | ||||||
| * | . | Kartik K. Agaram | 2022-01-02 | 1 | -1/+1 | |
| | | ||||||
| * | sandbox: tweaks to warning copy | Kartik K. Agaram | 2022-01-02 | 1 | -7/+8 | |
| | | ||||||
| * | sandbox: color tweaks | Kartik K. Agaram | 2022-01-02 | 1 | -4/+4 | |
| | | ||||||
| * | spacing | Kartik K. Agaram | 2021-12-26 | 1 | -0/+2 | |
| | | ||||||
| * | gemini.tlv: stop using default background | Kartik K. Agaram | 2021-12-25 | 1 | -2/+2 | |
| | | ||||||
| * | undo accidental color scheme commit | Kartik K. Agaram | 2021-12-25 | 1 | -1/+1 | |
| | | ||||||
| * | gemini: better error-handling | Kartik K. Agaram | 2021-12-25 | 1 | -5/+9 | |
| | | ||||||
| * | start persisting sandboxing settings | Kartik K. Agaram | 2021-12-25 | 1 | -0/+86 | |
| | | | | | Zero guarantees of compatibility at this point. | |||||
| * | reorg | Kartik K. Agaram | 2021-12-25 | 1 | -24/+24 | |
| | | ||||||