clean up a few more loose ends

[?]

Aug 14, 2022, 4:53 PM

MOAEVTKJCOJPY66OF74FOQIDQ4L2IP3JIKZLOYGHNRVKNQARSESAC

Dependencies

[2] OJBGNAN6 slight reorg in Readme
[3] UEE5W7WJ document one more shortcut
[4] 5BMR5HRT click to the left of a line
[5] PTDO2SOT add state arg to schedule_save
[6] A2TQYJ6J .
[7] E5FYDACS a likely source of issues
[8] QCPXQ2E3 add state arg to a few functions
[9] IDGP4BJZ new known issue with drawings
[10] F4QQIBEH clarify what "large files" means
[11] 5ED3YGHW planning out cursor up/down over wrapped lines
[12] 34TC5SYK record another known issue I don't know how to fix yet
[13] TCNHUMIW one more known issue
[14] VC2CU2GG faster paste
[15] MLG2OGU7 things seem to feel snappier now
[16] UGYRO7TO forgot to commit documentation for the commandline arg
[17] 73OCE2MC after much struggle, a brute-force undo
[18] CZRMAMSB clearer discription of how to run lines.love
[19] 242L3OQX bugfix: ensure Cursor_line is always on a text line
[20] AVFRVNFR better handle moving points
[21] EV36VCVF another known issue
[22] ZRKTXF4Q tweak to Readme
[23] VJ77YABH more efficient undo/redo
[24] FS2ITYYH record a known issue
[25] MD3W5IRA new fork: rip out drawing support
[26] D4FEFHQC flesh out Readme
[27] WLWNS6FB a bug I've never run into
[28] MTIS2XTC affirm a priority
[29] MTJEVRJR add state arg to a few functions
[30] TGHAJBES use line cache for drawings as well
[31] 2L5MEZV3 experiment: new edit namespace
[32] LF7BWEG4 group all editor globals
[33] BYG5CEMV support for naming points
[34] LNUHQOGH start passing in Editor_state explicitly
[35] ILOA5BYF separate data structure for each line's cache data

Change contents

edit in undo.lua at line 53

[5.928]→[5.1310:1349](∅→∅),[5.999]→[5.1310:1349](∅→∅),[5.1310]→[5.1310:1349](∅→∅),[5.1349]→[5.929:984](∅→∅)

current_drawing_mode=Drawing_mode,
previous_drawing_mode=State.previous_drawing_mode,
edit in edit.lua at line 259

[5.2037]→[5.15:104](∅→∅),[5.8570]→[5.15:104](∅→∅),[5.8139]→[5.15:104](∅→∅)

-- invalidate various cached bits of lines
State.lines.current_drawing = nil
edit in edit.lua at line 272

[5.8421]→[5.207:296](∅→∅)

-- invalidate various cached bits of lines
State.lines.current_drawing = nil
edit in README.md at line 33

[3.91]→[5.884:1117](∅→∅),[5.884]→[5.884:1117](∅→∅)

For shortcuts while editing drawings, consult the online help. Either:
* hover on a drawing and hit `ctrl+h`, or
* click on a drawing to start a stroke and then press and hold `h` to see your
options at any point during a stroke.
edit in README.md at line 50

[5.15]→[5.1190:1283](∅→∅),[2.170]→[5.1190:1283](∅→∅),[5.277]→[5.1190:1283](∅→∅),[5.148]→[5.1190:1283](∅→∅),[5.1283]→[5.16:17](∅→∅),[5.17]→[5.1283:1417](∅→∅),[5.1283]→[5.1283:1417](∅→∅),[5.1417]→[5.62:188](∅→∅),[5.188]→[5.18:19](∅→∅),[5.19]→[5.188:265](∅→∅),[5.188]→[5.188:265](∅→∅),[5.265]→[5.1583:1643](∅→∅),[5.1583]→[5.1583:1643](∅→∅),[5.1643]→[5.20:21](∅→∅),[5.21]→[5.18:135](∅→∅),[5.135]→[4.1171:1172](∅→∅)

* The text cursor will always stay on the screen. This can have some strange
implications:

* A long series of drawings will get silently skipped when you hit
page-down, until a line of text can be showed on screen.
* If there's no line of text at the top of the file, you may not be able
to scroll back up to the top with page-up.

So far this app isn't really designed for drawing-heavy files. For now I'm
targeting mostly-text files with a few drawings mixed in.

* No clipping yet for drawings. In particular, circles/squares/rectangles and
point labels can overflow a drawing.