| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | drop stale flag from documentation | Kartik K. Agaram | 2022-07-01 | 1 | -10/+0 |
| | | |||||
| * | ugh, handle absolute as well as relative paths | Kartik K. Agaram | 2022-07-01 | 2 | -1/+13 |
| | | |||||
| * | include CWD when saving filename | Kartik K. Agaram | 2022-07-01 | 1 | -1/+3 |
| | | |||||
| * | bugfix: clicking on empty lines | Kartik K. Agaram | 2022-07-01 | 2 | -1/+18 |
| | | |||||
| * | enforce press/release state only processed once | Kartik K. Agaram | 2022-07-01 | 1 | -4/+7 |
| | | | | | | | | | bugfix scenario: press pageup click somewhere near the bottom Before this change the selection was flickering when doing this. | ||||
| * | bugfix: manage screen_top and cursor when resizing | Kartik K. Agaram | 2022-07-01 | 3 | -0/+45 |
| | | |||||
| * | bugfix: enable resize when loading settings | Kartik K. Agaram | 2022-06-30 | 1 | -2/+10 |
| | | |||||
| * | right margin | Kartik K. Agaram | 2022-06-30 | 5 | -41/+114 |
| | | |||||
| * | start loading settings as applicable | Kartik K. Agaram | 2022-06-30 | 1 | -12/+43 |
| | | |||||
| * | start saving some settings to disk on quit | Kartik K. Agaram | 2022-06-30 | 1 | -1/+8 |
| | | | | | We're still not reading them anywhere. | ||||
| * | initialize screen width to something reasonable | Kartik K. Agaram | 2022-06-30 | 1 | -3/+3 |
| | | |||||
| * | rip out geometry commandline arg | Kartik K. Agaram | 2022-06-30 | 1 | -33/+8 |
| | | | | | Let's try really hard to ignore the terminal. | ||||
| * | use the background color | Kartik K. Agaram | 2022-06-30 | 1 | -2/+2 |
| | | | | | | I'd hoped this would reduce the blocks of black while resizing, but it doesn't seem to have made a difference. | ||||
| * | stop blanking screen while resizing | Kartik K. Agaram | 2022-06-30 | 1 | -9/+0 |
| | | |||||
| * | rip out notion of Line_width | Kartik K. Agaram | 2022-06-30 | 6 | -163/+67 |
| | | |||||
| * | rip out the line-width slider | Kartik K. Agaram | 2022-06-30 | 2 | -48/+0 |
| | | | | | | | | New plan: - render text across the whole window - let people resize the window to the desired line width - save window size settings between sessions | ||||
| * | bugfix: lines that aren't drawn from the start | Kartik K. Agaram | 2022-06-30 | 3 | -11/+48 |
| | | | | | | | | | | | | | | | | I can't believe I didn't catch this until now. All I had to do is open MobyDick.markdown from https://www.hogbaysoftware.com/posts/moby-dick-workout, press page-down and click on the top screen line (or any screen line containing the same line as the top screen line). Easy to catch with any file containing lots of overly long lines, as happens in particular at the start of Moby Dick. I _had_ seen this problem before, but it seemed to disappear after unrelated changes, and I convinced myself I'd fixed it as a side-effect. The bug just failed to manifest if the top line happened to start at the top of the screen. Scroll down a few pages in Moby Dick and the dialogue starts and line length drops precipitously. | ||||
| * | some redundant calls | Kartik K. Agaram | 2022-06-30 | 1 | -4/+0 |
| | | |||||
| * | bugfix: save previous file when dropping a new one on | Kartik K. Agaram | 2022-06-29 | 2 | -0/+35 |
| | | |||||
| * | new test: dragging and dropping a file on lines.love | Kartik K. Agaram | 2022-06-29 | 1 | -0/+27 |
| | | |||||
| * | avoid redundant writes on exit | Kartik K. Agaram | 2022-06-29 | 1 | -1/+3 |
| | | |||||
| * | clarify what "large files" means | Kartik K. Agaram | 2022-06-29 | 1 | -1/+2 |
| | | |||||
| * | clicking to the right of a line within line width | Kartik K. Agaram | 2022-06-29 | 2 | -1/+38 |
| | | |||||
| * | . | Kartik K. Agaram | 2022-06-29 | 1 | -1/+1 |
| | | |||||
| * | bugfix: clicking past end of screen line | Kartik K. Agaram | 2022-06-29 | 2 | -1/+50 |
| | | | | | I could swear I checked this at some point. But I didn't have a test! | ||||
| * | bugfix: scrolling in left/right movements | Kartik K. Agaram | 2022-06-28 | 2 | -10/+148 |
| | | | | | | I'd always had a funny feeling there was something missing there but somehow never thought of the right failing test. | ||||
| * | when naming points, allow backspacing back to '' | Kartik K. Agaram | 2022-06-27 | 1 | -0/+1 |
| | | |||||
| * | undo commit 861c57b533 | Kartik K. Agaram | 2022-06-27 | 1 | -2/+1 |
| | | | | | | Turns out ctrl+ makes it into lua.textinput. Thanks John Blommers for the report. This should fix https://github.com/akkartik/lines.love/issues/6. | ||||
| * | bugfix: typing a capital letter deletes selection | Kartik K. Agaram | 2022-06-26 | 3 | -3/+29 |
| | | |||||
| * | bugfix: deleting a selection spanning pages | Kartik K. Agaram | 2022-06-26 | 2 | -0/+29 |
| | | |||||
| * | bugfix: clear selection in a couple more places | Kartik K. Agaram | 2022-06-23 | 1 | -0/+2 |
| | | |||||
| * | bugfix: don't delete selection when moving cursor | Kartik K. Agaram | 2022-06-23 | 3 | -1/+23 |
| | | |||||
| * | record one more case I can't automatically detect | Kartik K. Agaram | 2022-06-23 | 1 | -0/+5 |
| | | |||||
| * | fix a failing test | Kartik K. Agaram | 2022-06-23 | 1 | -4/+2 |
| | | | | | | I deployed this without even running it once :/ Production was broken for 9 minutes until I rolled back. | ||||
| * | extract a function | Kartik K. Agaram | 2022-06-23 | 2 | -18/+14 |
| | | |||||
| * | bugfix: recompute screen lines in backspace/delete | Kartik K. Agaram | 2022-06-23 | 1 | -0/+4 |
| | | | | | | | | | Scenario: backspacing until a line takes up fewer screen lines, then pressing `down`. I've gone through and checked that fragments and screen_line_starting_pos are now cleared together everywhere. | ||||
| * | keep drawings within the line width slider as well | Kartik K. Agaram | 2022-06-22 | 3 | -29/+30 |
| | | |||||
| * | show the line width when dragging the slider | Kartik K. Agaram | 2022-06-22 | 1 | -0/+4 |
| | | |||||
| * | turns out super- chords to get to textinput | Kartik K. Agaram | 2022-06-22 | 1 | -2/+1 |
| | | |||||
| * | bugfix: delete selection before pasting | Kartik K. Agaram | 2022-06-21 | 3 | -3/+41 |
| | | |||||
| * | bugfix | Kartik K. Agaram | 2022-06-21 | 2 | -1/+8 |
| | | | | | | State changes when inserting return are now in sync with other characters. | ||||
| * | better fix for commit 3ffc2ed8f | Kartik K. Agaram | 2022-06-20 | 1 | -0/+1 |
| | | | | | | | | | | I'm giving up finding a more generalized solution. The issue is that we need the correct selection state right up to the point where we modify Lines, in order to capture precise undo state. Hopefully there aren't any other keychords that should clear the selection. | ||||
| * | revert selection logic to before commit 3ffc2ed8f | Kartik K. Agaram | 2022-06-20 | 3 | -8/+12 |
| | | | | | | We still have a failing test, but now it's the one we introduced in commit 3ffc2ed8f. | ||||
| * | snapshot: test for a new regression | Kartik K. Agaram | 2022-06-20 | 1 | -0/+22 |
| | | | | | | | Caused by commit 3ffc2ed8f. We might need to bring back a lot of complexity for this. | ||||
| * | selection bugfix | Kartik K. Agaram | 2022-06-20 | 2 | -1/+19 |
| | | |||||
| * | much simpler | Kartik K. Agaram | 2022-06-20 | 2 | -31/+8 |
| | | | | | | | | | We just need to ensure textinput events never make use of selection state. All tests are passing, but I'm aware of a couple of issues. But now we can keep all the special cases in one place. | ||||
| * | some early returns should be asserts | Kartik K. Agaram | 2022-06-20 | 1 | -1/+3 |
| | | |||||
| * | move Selection1 clearing past business logic | Kartik K. Agaram | 2022-06-20 | 1 | -10/+10 |
| | | | | | | | Now all the cases that clear Selection1 do so in a very consistent way at the end of each case. And cases that set Selection1 symmetrically do so at the start of each case. | ||||
| * | remove some redundant checks | Kartik K. Agaram | 2022-06-20 | 1 | -30/+10 |
| | | | | | Now all the cases manage Selection1 similarly. | ||||
| * | no, that's not right | Kartik K. Agaram | 2022-06-20 | 3 | -3/+40 |
| | | | | | | | | | | | | | | | Bugfix: we want selections to persist even when we lift up the shift key. This requires hoisting some code inside every case inside the whole keypress hierarchy, to ensure we never clear selections before textinput events can handle them. Current cross-cutting concerns we're explicitly scattering code for. - autosave - undo - selection management | ||||