about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* fix stale commentKartik K. Agaram2023-01-011-1/+1
|
* bugfixKartik K. Agaram2022-12-242-2/+2
| | | | | | | | | | | Scenario: make some edits, select some text, make some more edits. Press ctrl-z. Before this commit, undo would stop at the point of selection and previous edits would become unreachable. After this commit, both ctrl-z and ctrl-y seem able to span the point of selection.
* typoKartik K. Agaram2022-12-242-2/+2
|
* fix some arg namesKartik K. Agaram2022-12-231-3/+3
|
* another missed renameKartik K. Agaram2022-12-231-2/+2
|
* overzealous search-and-replaceKartik K. Agaram2022-12-232-2/+2
|
* consistent names in a few more placesKartik K. Agaram2022-12-236-16/+16
|
* make love event names consistentKartik K. Agaram2022-12-2315-163/+163
| | | | | 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.
* require editor margins to be intsKartik K. Agaram2022-12-232-2/+5
| | | | | | | | | | | | Not directly relevant here, but forks of this project that permit zooming can run into weird glitches if margins are not a whole number of pixels. I'd always assumed a type system that divided ints into floats was strictly superior, but now I have experienced a situation where requiring ints isn't just a compromise for the underlying CPU implementation. Particularly since Lua's print() silently hides really tiny fractions.
* streamline one more test nameKartik K. Agaram2022-12-132-28/+28
|
* repeat changes on source editorKartik K. Agaram2022-12-131-53/+36
|
* more streamlined test namesKartik K. Agaram2022-12-131-29/+29
| | | | https://lobste.rs/messages/e1rimy
* remove a duplicate testKartik K. Agaram2022-12-131-27/+10
|
* repeat bugfix on source editor X-(Kartik K. Agaram2022-12-121-2/+5
|
* switch one call back to keychord_pressedKartik K. Agaram2022-12-121-1/+1
| | | | I don't understand why, but we need to fix production.
* switch a bunch of tests to textinput eventsKartik K. Agaram2022-12-121-18/+18
| | | | | textinput is strictly more realistic than keychord_pressed, which doesn't cause any textinput events. Use it wherever possible.
* bugfix in changing shape mid-strokeKartik K. Agaram2022-12-122-3/+6
|
* repeat bugfix on source editorKartik 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.
* save state when clearing logsKartik K. Agaram2022-12-051-0/+2
|
* 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.
* compare nested tablesKartik K. Agaram2022-11-301-2/+2
|
* repeat bugfix on source editorKartik K. Agaram2022-11-271-1/+1
|
* bugfixKartik K. Agaram2022-11-271-1/+1
|
* undo an ancient hack; be an idiomatic LÖVE appKartik K. Agaram2022-11-271-3/+3
|
* ctrl+a: select entire bufferKartik K. Agaram2022-11-193-2/+9
|
* 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.
* 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.
* stop tracking wallclock timeKartik K. Agaram2022-11-035-24/+26
| | | | We only need time differences.
* fix support for absolute paths in WindowsKartik K. Agaram2022-09-262-0/+2
|
* 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
|
* 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.
* indentKartik K. Agaram2022-09-181-7/+7
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-25 05:01:55 +0000