about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* bugfix for non-ASCIIKartik K. Agaram2022-05-291-3/+4
|
* update some documentationKartik K. Agaram2022-05-291-3/+6
|
* extract a couple of methodsKartik K. Agaram2022-05-281-5/+25
|
* bugfix: include shift keys in modifier_downKartik K. Agaram2022-05-281-3/+25
|
* extract a couple more methodsKartik K. Agaram2022-05-281-26/+34
|
* move some codeKartik K. Agaram2022-05-282-28/+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
|
* .Kartik K. Agaram2022-05-271-1/+1
|
* tweak modifier keys to include 'shift'Kartik K. Agaram2022-05-271-1/+4
|
* paste in text with M-vKartik K. Agaram2022-05-262-0/+13
|
* .Kartik K. Agaram2022-05-251-1/+0
|
* few more transitions between shapesKartik K. Agaram2022-05-251-2/+10
|
* typosKartik K. Agaram2022-05-251-2/+2
|
* M-left/M-right for word-based motionsKartik K. Agaram2022-05-252-0/+23
|
* 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
|
* assert for a bug I saw a while ago but can no longer reproduceKartik K. Agaram2022-05-251-0/+1
| | | | | I saw screen_top not at start of screen line, but at cursor location in middle of line.
* 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-252-1/+24
|
* no, make sure to compute line width after screen dimensionsKartik K. Agaram2022-05-253-6/+8
|
* couple more testsKartik K. Agaram2022-05-254-18/+83
| | | | 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-232-16/+6
|
* keep one screen line of overlap on pagedownKartik K. Agaram2022-05-232-19/+44
| | | | | | | | | | | | | | | | | | | | 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-232-10/+107
| | | | 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-232-3/+69
| | | | 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-233-25/+25
|
* quite the frustrating bugfixKartik K. Agaram2022-05-231-5/+7
|
* snapshotKartik K. Agaram2022-05-232-22/+169
| | | | Why the fuck is this so fucking hard?
* .Kartik K. Agaram2022-05-231-1/+2
|
* similar tests for cursor upKartik K. Agaram2022-05-231-1/+67
|
* couple of tests for cursor downKartik K. Agaram2022-05-232-8/+68
|
* bugfix: don't rely on Screen_bottom1 while scrollingKartik K. Agaram2022-05-233-12/+23
| | | | | Setting up the test just right to test the thing I want to test was a rube goldberg machine of constants.
* first successful pagedown test, first bug found by testKartik K. Agaram2022-05-234-14/+86
| | | | | | | | | | | | | | | | | | | I also really need to rethink how people debug my programs. My approach of inserting and deleting print() takes a lot of commitment. I need my old trace-based whitebox testing idea. However, in my past projects I never did figure out a good framework for tweaking how verbose a trace to emit. Perhaps that's too many knobs. Perhaps we just need a way to run a single test with the most verbose trace possible. Then it's just a matter of having the trace tell a coherent story? But even if the trace stays out of program output in that situation, it's still in the programmer's face in the _code_. Ugh. Current plan: ship program with maximum tests and zero commented-out prints. If you want to debug, insert prints. This is better than previous, text-mode, projects just by virtue of the stdout channel being dedicated to debug stuff.
* first test!Kartik K. Agaram2022-05-222-12/+87
|
* fold variables for screen dimensions into the app frameworkKartik K. Agaram2022-05-221-8/+8
|
* one more implicationKartik K. Agaram2022-05-221-0/+3
|
* basic test-enabled frameworkKartik K. Agaram2022-05-224-34/+251
| | | | | Tests still have a lot of side-effects on the real screen. We'll gradually clean those up.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-02 13:02:00 +0000