about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* Merge lines.loveKartik K. Agaram2022-12-121-1/+6
|\
| * repeat bugfix on source editorKartik K. Agaram2022-12-121-1/+6
| |
* | Merge lines.loveKartik K. Agaram2022-12-121-1/+6
|\|
| * bugfix: naming points in drawingsKartik K. Agaram2022-12-121-1/+6
| | | | | | | | | | | | | | | | | | We had a regression since commit 60e1023f0 on Nov 27. Turns out we do need the ancient hack after all. But no, we won't go back to the hack. It's a simple problem to fix right. And while we're at it, we'll fix the test harness to be more realistic so it would have caught this problem.
* | Merge lines.loveKartik K. Agaram2022-12-051-0/+2
|\|
| * save state when clearing logsKartik K. Agaram2022-12-051-0/+2
| |
* | Merge lines.loveKartik K. Agaram2022-12-052-0/+13
|\|
| * source editor: clear logsKartik K. Agaram2022-12-052-0/+11
| |
| * consume a mouse click when switching sidesKartik K. Agaram2022-12-051-0/+2
| | | | | | | | This way we can have the log side actually take focus sometimes.
* | Merge lines.loveKartik K. Agaram2022-11-301-2/+2
|\|
| * compare nested tablesKartik K. Agaram2022-11-301-2/+2
| |
* | irrelevant issue fork this forkKartik K. Agaram2022-11-301-4/+0
| |
* | include a few more forksKartik K. Agaram2022-11-301-0/+7
| |
* | Merge lines.loveKartik K. Agaram2022-11-271-1/+1
|\|
| * repeat bugfix on source editorKartik K. Agaram2022-11-271-1/+1
| |
* | Merge lines.loveKartik K. Agaram2022-11-271-1/+1
|\|
| * bugfixKartik K. Agaram2022-11-271-1/+1
| |
* | Merge lines.loveKartik K. Agaram2022-11-271-3/+3
|\|
| * undo an ancient hack; be an idiomatic LÖVE appKartik K. Agaram2022-11-271-3/+3
| |
* | Merge lines.loveKartik K. Agaram2022-11-193-2/+9
|\|
| * ctrl+a: select entire bufferKartik K. Agaram2022-11-193-2/+9
| |
* | Merge lines.loveKartik K. Agaram2022-11-111-4/+14
|\|
| * source editing: highlight [[ ]] comments/stringsKartik K. Agaram2022-11-111-4/+14
| | | | | | | | | | In the process I fixed suffix detection for patterns with more than 1 character.
* | Merge lines.loveKartik K. Agaram2022-11-061-1/+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.
* | purge unused button infrastructureKartik K. Agaram2022-11-051-6/+0
| |
* | Merge lines.loveKartik K. Agaram2022-11-035-24/+26
|\|
| * stop tracking wallclock timeKartik K. Agaram2022-11-035-24/+26
| | | | | | | | We only need time differences.
* | Merge lines.loveKartik K. Agaram2022-09-262-0/+2
|\|
| * fix support for absolute paths in WindowsKartik K. Agaram2022-09-262-0/+2
| |
* | Merge lines.loveKartik K. Agaram2022-09-194-48/+105
|\|
| * migrate old settings, attempt #3Kartik K. Agaram2022-09-192-2/+44
| | | | | | | | | | This time we have to handle absolute filenames. Now lines-polygon-experiment fork should merge successfully, at least.
| * ugh, missed deleting an argKartik K. Agaram2022-09-191-1/+1
| |
| * handle missing cursors in settingsKartik K. Agaram2022-09-191-3/+9
| |
| * 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
| |
| * source: load cursor position from settingsKartik K. Agaram2022-09-191-2/+5
| |
| * source: no commandline argsKartik K. Agaram2022-09-191-15/+4
| |
| * source: remember cursor position of multiple filesKartik K. Agaram2022-09-191-4/+12
| |
| * source: support only relative paths within the appKartik K. Agaram2022-09-191-5/+2
| |
| * bugfix: mouse clicks on file navigator above log browser sideKartik K. Agaram2022-09-181-0/+5
| |
| * support special chars like '(' in searchKartik K. Agaram2022-09-181-8/+8
| |
* | Merge lines.loveKartik K. Agaram2022-09-188-28/+235
|\|
| * delete a duplicate filename candidateKartik K. Agaram2022-09-181-1/+0
| |
| * filter candidates in file navigatorKartik K. Agaram2022-09-182-1/+46
| |
| * hide editor cursor while in file navigatorKartik K. Agaram2022-09-183-6/+6
| |
| * bugfix: disable typing while file navigator is openKartik K. Agaram2022-09-181-0/+3
| |
| * support mouse clicks in file navigatorKartik K. Agaram2022-09-182-2/+13
| |
| * start showing source menu file navigation state graphicallyKartik K. Agaram2022-09-182-5/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.