clean up some issues I now feel confident about

akkartik
Sep 1, 2024, 2:16 AM
WYK3HCQDVOQACXJTYDG7ZKDUNYBF66T4XY3ZY7JWYOPY6DVLTZ3AC

Dependencies

  • [2] F4QQIBEH clarify what "large files" means
  • [3] MTIS2XTC affirm a priority
  • [4] 242L3OQX bugfix: ensure Cursor_line is always on a text line
  • [5] MLG2OGU7 things seem to feel snappier now
  • [6] VJ77YABH more efficient undo/redo
  • [7] IDGP4BJZ new known issue with drawings
  • [8] A2TQYJ6J .
  • [9] 73OCE2MC after much struggle, a brute-force undo
  • [10] MTJEVRJR add state arg to a few functions
  • [11] VC2CU2GG faster paste
  • [12] TCNHUMIW one more known issue
  • [13] 34TC5SYK record another known issue I don't know how to fix yet
  • [14] EV36VCVF another known issue
  • [15] FS2ITYYH record a known issue
  • [16] OJBGNAN6 slight reorg in Readme

Change contents

  • replacement in undo.lua at line 4
    [4.154][4.154:319]()
    -- Incredibly inefficient; we make a copy of lines on every single keystroke.
    -- The hope here is that we're either editing small files or just reading large files.
    [4.154]
    [4.319]
    -- makes a copy of lines on every single keystroke; will be inefficient with really long lines.
  • edit in README.md at line 53
    [4.62][4.14:15](),[3.66][4.14:15](),[4.2477][4.14:15](),[4.8558][4.14:15](),[4.148][4.14:15](),[4.15][4.18:95](),[4.95][2.19:101]()
    * Undo/redo may be sluggish in large files. Large files may grow sluggish in
    other ways. lines.love works well in all circumstances with files under
    50KB.
  • edit in README.md at line 54
    [4.277][4.63:170]()
    * If you kill the process, say by force-quitting because things things get
    sluggish, you can lose data.