about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* done passing left/right margins everywhereKartik K. Agaram2022-07-081-16/+16
| | | | | | | The final step is to add them to: - Text.compute_fragments Doing it carefully caught 5 call-sites that my tests didn't catch.
* add args to some functionsKartik K. Agaram2022-07-081-14/+14
| | | | - Text.populate_screen_line_starting_pos
* add args to some functionsKartik K. Agaram2022-07-081-6/+6
| | | | - Text.to2
* add args to some functionsKartik K. Agaram2022-07-081-5/+5
| | | | - Text.previous_screen_line
* add args to some functionsKartik K. Agaram2022-07-082-11/+11
| | | | - Text.snap_cursor_to_bottom_of_screen
* add args to some functionsKartik K. Agaram2022-07-081-10/+12
| | | | - Text.nearest_cursor_pos
* add args to some functionsKartik K. Agaram2022-07-081-3/+3
| | | | - Text.move_cursor_down_to_next_text_line_while_scrolling_again_if_necessary
* add args to some functionsKartik K. Agaram2022-07-081-2/+2
| | | | - Text.cursor_at_final_screen_line
* add args to some functionsKartik K. Agaram2022-07-083-8/+8
| | | | - Text.pos_at_start_of_cursor_screen_line
* add args to some functionsKartik K. Agaram2022-07-083-6/+5
| | | | - Text.to_pos_on_line
* indentKartik K. Agaram2022-07-082-3/+12
|
* add args to some functionsKartik K. Agaram2022-07-083-5/+5
| | | | - Text.in_line
* add args to some functionsKartik K. Agaram2022-07-083-15/+15
| | | | | | | | | - Text.clip_selection - Text.cut_selection - Text.delete_selection - Text.delete_selection_without_undo - Text.mouse_pos - Text.to_pos
* add args to some functionsKartik K. Agaram2022-07-081-28/+28
| | | | | | | | | | | | - Text.pageup - Text.pagedown - Text.up - Text.down - Text.end_of_line - Text.word_left - Text.word_right - Text.left - Text.right
* start passing left/right margins everywhereKartik K. Agaram2022-07-082-10/+10
| | | | | | | | | | | I have a set of changes that passes all tests, but I'm going to commit them very carefully to ensure I don't miss any call-sites. In this commit I'm adding the args to: - Text.draw - Text.tweak_screen_top_and_cursor But calls within them don't yet pass them where they should. In this manner I'm going to progress systematically from the top down.
* rename a couple of variablesKartik K. Agaram2022-07-081-10/+10
|
* affirm a priorityKartik K. Agaram2022-07-081-0/+2
|
* drop an arg from a functionKartik K. Agaram2022-07-083-4/+4
|
* switch arg for a functionKartik K. Agaram2022-07-082-16/+12
|
* stop scanning from start of file on every App.drawKartik K. Agaram2022-07-071-40/+38
|
* yet another bugfix in selection managementKartik K. Agaram2022-07-072-20/+6
| | | | | | | | | | Thanks Leonard Schütz for the report! Failing scenario: click to move cursor hit backspace First backspace wasn't being doing anything earlier.
* just keep the cursor visible after any input eventsKartik K. Agaram2022-07-061-2/+8
| | | | This is much nicer.
* show cursor immediately after a mouse clickKartik K. Agaram2022-07-061-0/+2
| | | | | I've been subtly finding myself waiting for the cursor to stop blinking to see if I clicked on the right place.
* better error messageKartik K. Agaram2022-07-051-0/+3
| | | | https://tildegit.org/akkartik/lines.love/issues/1
* make freehand drawings smootherKartik K. Agaram2022-07-051-1/+17
| | | | | | | | | | | | Now I might actually use them more, and maybe I can start considering taking out some shapes. Do I really need circles if I don't provide ellipses? Thanks Ivan Reese for the feedback. "What drawings does your tool encourage?" Minor note: taking out the deepcopy creates a cute little string like effect, where the curve grows tighter the slower you draw it.
* optimization: moving cursor to next wordKartik K. Agaram2022-07-051-4/+12
|
* bugfix: avoid scrolling on 'end'Kartik K. Agaram2022-07-052-8/+15
| | | | | There's multiple ways to do this, only one of them is right, and I keep forgetting what it is. Turn it into a method.
* bugfix: 'escape' to cancel a strokeKartik K. Agaram2022-07-053-6/+28
| | | | | | This has been broken since commit b544e8c357 on May 17 :/ I'm just undoing that commit, which turns out to be completely unnecessary. And adding a test.
* what should happen to selection while drawing?Kartik K. Agaram2022-07-051-0/+1
| | | | First idea: just leave it alone. Let's see how this works.
* keep online help inside of drawingKartik K. Agaram2022-07-041-2/+2
|
* bugfixKartik K. Agaram2022-07-031-1/+1
| | | | Gracefully degrade if previously edited file shrinks.
* link to export toolKartik K. Agaram2022-07-021-0/+5
|
* deemphasize the terminal in ReadmeKartik K. Agaram2022-07-011-22/+4
|
* drop stale flag from documentationKartik K. Agaram2022-07-011-10/+0
|
* ugh, handle absolute as well as relative pathsKartik K. Agaram2022-07-012-1/+13
|
* include CWD when saving filenameKartik K. Agaram2022-07-011-1/+3
|
* bugfix: clicking on empty linesKartik K. Agaram2022-07-012-1/+18
|
* enforce press/release state only processed onceKartik K. Agaram2022-07-011-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 resizingKartik K. Agaram2022-07-013-0/+45
|
* bugfix: enable resize when loading settingsKartik K. Agaram2022-06-301-2/+10
|
* right marginKartik K. Agaram2022-06-305-41/+114
|
* start loading settings as applicableKartik K. Agaram2022-06-301-12/+43
|
* start saving some settings to disk on quitKartik K. Agaram2022-06-301-1/+8
| | | | We're still not reading them anywhere.
* initialize screen width to something reasonableKartik K. Agaram2022-06-301-3/+3
|
* rip out geometry commandline argKartik K. Agaram2022-06-301-33/+8
| | | | Let's try really hard to ignore the terminal.
* use the background colorKartik K. Agaram2022-06-301-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 resizingKartik K. Agaram2022-06-301-9/+0
|
* rip out notion of Line_widthKartik K. Agaram2022-06-306-163/+67
|
* rip out the line-width sliderKartik K. Agaram2022-06-302-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 startKartik K. Agaram2022-06-303-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.