about summary refs log tree commit diff stats
path: root/text.lua
Commit message (Collapse)AuthorAgeFilesLines
* extract a new variableKartik K. Agaram2022-06-021-93/+61
|
* crisp font renderingKartik K. Agaram2022-06-021-193/+135
|
* find textKartik K. Agaram2022-06-021-4/+76
|
* scroll if necessary on pasteKartik K. Agaram2022-06-021-0/+23
|
* renameKartik K. Agaram2022-06-021-2/+2
|
* test harness now supports copy/pasteKartik K. Agaram2022-06-021-3/+68
|
* bugfix: pasting newlinesKartik K. Agaram2022-06-021-12/+21
|
* more efficient undo/redoKartik K. Agaram2022-06-021-56/+36
| | | | | Now the bottleneck shifts to applying undo/redo in large files. But things should be snappy if you don't use the sluggish feature.
* renameKartik K. Agaram2022-06-021-12/+12
|
* this implementation undo load-tests quite poorlyKartik K. Agaram2022-06-021-0/+28
| | | | | | Even a 10KB file gets sluggish within the first 1k characters inserted. We're not running out of memory, we're just overloading Lua's GC.
* after much struggle, a brute-force undoKartik K. Agaram2022-06-021-0/+125
| | | | | | | | | Incredibly inefficient, but I don't yet know how to efficiently encode undo mutations that can span multiple lines. There seems to be one bug related to creating new drawings; they're not spawning events and undoing past drawing creation has some weird artifacts. Redo seems to consistently work, though.
* avoid scrolling down if possibleKartik K. Agaram2022-05-301-1/+28
|
* support non-text lines in Text.to2Kartik K. Agaram2022-05-301-1/+3
| | | | | Originally I was only using it on cursor line, but there's no reason that has to be true in general.
* regression: typing uppercase letters in textKartik K. Agaram2022-05-301-1/+1
|
* .Kartik K. Agaram2022-05-291-4/+4
|
* cut/copy selected text to clipboardKartik K. Agaram2022-05-291-0/+45
|
* selecting text and deleting selectionsKartik K. Agaram2022-05-291-4/+291
| | | | | | I've written a few tests for delete_selection, but the way different operations initialize the selection seems fairly standard and not worth testing so far.
* bugfix for non-ASCIIKartik K. Agaram2022-05-291-3/+4
|
* extract a couple of methodsKartik K. Agaram2022-05-281-5/+25
|
* extract a couple more methodsKartik K. Agaram2022-05-281-26/+34
|
* move some codeKartik K. Agaram2022-05-281-0/+28
| | | | | I had this idea originally to keep text.lua oblivious to drawings. But that hasn't been true for some time. Losing battle.
* extract a few methodsKartik K. Agaram2022-05-281-107/+121
|
* moveKartik K. Agaram2022-05-281-36/+38
|
* .Kartik K. Agaram2022-05-281-1/+1
|
* scroll on backspaceKartik K. Agaram2022-05-281-0/+68
|
* .Kartik K. Agaram2022-05-281-4/+4
|
* .Kartik K. Agaram2022-05-281-8/+8
|
* fix a regression in line wrappingKartik K. Agaram2022-05-281-1/+44
|
* scroll on enterKartik K. Agaram2022-05-281-0/+36
|
* paste in text with M-vKartik K. Agaram2022-05-261-0/+8
|
* M-left/M-right for word-based motionsKartik K. Agaram2022-05-251-0/+22
|
* extract couple of functionsKartik K. Agaram2022-05-251-34/+42
|
* couple of renamesKartik K. Agaram2022-05-251-23/+14
|
* keep repeated cursor up/down motions from drifting leftKartik K. Agaram2022-05-251-1/+5
|
* bugfix: don't append metadata when it already existsKartik K. Agaram2022-05-251-2/+6
|
* bugfixKartik K. Agaram2022-05-251-0/+41
| | | | | I spent 20 minutes converting a manual test to a reproducible automated one, but in the process I knew exactly what the problem was. Nice.
* test and App helper for mouse clicksKartik K. Agaram2022-05-251-1/+18
|
* no, make sure to compute line width after screen dimensionsKartik K. Agaram2022-05-251-1/+2
|
* couple more testsKartik K. Agaram2022-05-251-0/+45
| | | | Along with the App helpers needed for them.
* bugfix: down arrow doesn't scroll up unnecessarilyKartik K. Agaram2022-05-241-4/+46
| | | | up arrow doesn't seem to have the symmetric issue.
* bugfixKartik K. Agaram2022-05-241-5/+46
| | | | Found while reading https://www.gutenberg.org/ebooks/52091
* get rid of debug variablesKartik K. Agaram2022-05-231-7/+2
|
* keep one screen line of overlap on pagedownKartik K. Agaram2022-05-231-18/+43
| | | | | | | | | | | | | | | | | | | | I'm now extracting the concern of computing line.screen_line_starting_pos out of Text.draw. Earlier I had to make sure I ran through the whole line to compute screen_line_starting_pos, but that had the side-effect of updating Screen_bottom1.pos as well with lines that had never been rendered. In this process I hit my first bug due to an accidental global. It doesn't show up in the patch because I accidentally deleted a local declaration. (I thought I didn't need screen_line_starting_pos anymore, deleted everywhere, then brought it back everywhere from the bottom of the function up, but forgot to put back the very first occurrence.) The amount of yoyoing this caused between App.draw and Text.draw, I very much have spaghetti on my hands. Accidental globals are _terrible_ in a program with tests. Cross test contamination X-(
* a few tests for pageup, and a bugfixKartik K. Agaram2022-05-231-0/+89
| | | | It wasn't screen-line aware. Now it is.
* clean up test progress indicatorsKartik K. Agaram2022-05-231-11/+11
|
* one bug I've repeatedly run into while testing with Moby DickKartik K. Agaram2022-05-231-3/+68
| | | | https://www.hogbaysoftware.com/posts/moby-dick-workout
* scrolling with up arrowKartik K. Agaram2022-05-231-20/+19
|
* disable all debug printsKartik K. Agaram2022-05-231-22/+22
|
* quite the frustrating bugfixKartik K. Agaram2022-05-231-5/+7
|
* snapshotKartik K. Agaram2022-05-231-21/+161
| | | | Why the fuck is this so fucking hard?
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-06-30 22:48:32 +0000