about summary refs log tree commit diff stats
path: root/commands.lua
Commit message (Collapse)AuthorAgeFilesLines
* make love event names consistentKartik K. Agaram2022-12-231-2/+2
| | | | | I want the words to be easy to read, and to use a consistent tense. update and focus seem more timeless; let's make everything like those.
* source editor: clear logsKartik K. Agaram2022-12-051-0/+1
|
* show partial items in the menuKartik K. Agaram2022-11-061-1/+1
| | | | | Seeing a partial item can nudge someone to try resizing the window and so learn about more shortcuts.
* source: show files in MRU orderKartik K. Agaram2022-09-191-4/+8
| | | | | I'm not going to save this MRU order across sessions for now. It's good enough to save cursor positions for individual files, I think.
* extract a couple of functionsKartik K. Agaram2022-09-191-13/+16
|
* filter candidates in file navigatorKartik K. Agaram2022-09-181-0/+42
|
* support mouse clicks in file navigatorKartik K. Agaram2022-09-181-2/+9
|
* start showing source menu file navigation state graphicallyKartik K. Agaram2022-09-181-5/+53
| | | | | | | | | | | | | | | | | | | | | | I'm a bit leery of going down this road: - If there's a bug in how I render logs graphically that could be extremely misleading. Perhaps this suggests that the code to log things should be significantly simpler than the code that might be debugged. If writing the debug helper requires all my smarts I'm not smart enough to debug using the helper, etc. Given this idea, the fact that I'm copying production code into the logging helper is concerning. - There's a question of what code it's ok for logging helpers to depend on. This is an issue shared with tests. I often implicitly (and without meaning to) assume the presence of some well-tested helpers when writing tests. If those helpers ever break I can get into a rabbit hole of debugging. This problem might be even more insidious with logging helpers that will give me no indication when they break. Still and all, it's cool to see menus in my logs. Let's see if it's useful.
* source: up/down in file navigatorKartik K. Agaram2022-09-181-0/+68
| | | | I'm starting to use logging, but it's still easier to print textual logs.
* indentKartik K. Agaram2022-09-181-7/+7
|
* source: show all files in navigatorKartik K. Agaram2022-09-171-5/+31
| | | | | We still don't have up/down arrow keys. And we still don't have the ability to filter filenames by typing.
* renameKartik K. Agaram2022-09-171-3/+3
|
* delete some logsKartik K. Agaram2022-09-171-3/+0
| | | | | | | One open question is how to manage logs while drawing, since they can be extremely verbose. Neither tags nor depths seem like the right metaphor here, and that gives me pause that I perhaps don't see the full space of needs yet.
* bugfix: never skip files in file navigatorKartik K. Agaram2022-09-171-4/+3
|
* use existing localKartik K. Agaram2022-09-171-1/+1
|
* use a helperKartik K. Agaram2022-09-171-11/+7
|
* some debug printsKartik K. Agaram2022-09-171-0/+4
| | | | | | I'm starting to edit the sources from within the app in ernest. First question: why does the file navigation menu skip some files? These prints answer the question.
* switch shortcuts for bifold textKartik K. Agaram2022-09-061-3/+3
| | | | | | I've been running out of ctrl+ shortcuts, and I just remembered my original idea to keep ctrl+ for drawings/mouse operations and alt+ for everything else.
* support drawings in the source editorKartik K. Agaram2022-09-051-1/+1
|
* editing source code from within the appKartik K. Agaram2022-09-031-0/+100
integrated from pong.love via text.love: https://merveilles.town/@akkartik/108933336531898243
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-20 15:37:51 +0000