about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2024-08-31 19:16:20 -0700
committerKartik K. Agaram <vc@akkartik.com>2024-08-31 19:16:20 -0700
commit52f876302f7e6da1f8f418d9dc85f0698c494e15 (patch)
tree3a3b7078d8a842c36bed8c141994bcf4c1f4feeb
parentf98cdd14fd876f57a8dc753316fc27994242828f (diff)
downloadview.love-52f876302f7e6da1f8f418d9dc85f0698c494e15.tar.gz
clean up some issues I now feel confident about
-rw-r--r--README.md7
-rw-r--r--undo.lua3
2 files changed, 1 insertions, 9 deletions
diff --git a/README.md b/README.md
index de57872..7e9ac31 100644
--- a/README.md
+++ b/README.md
@@ -51,13 +51,6 @@ found anything amiss: http://akkartik.name/contact
 
 * No support yet for right-to-left languages.
 
-* 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.
-
-* If you kill the process, say by force-quitting because things things get
-  sluggish, you can lose data.
-
 * The text cursor will always stay on the screen. This can have some strange
   implications:
 
diff --git a/undo.lua b/undo.lua
index d91fecd..59ca481 100644
--- a/undo.lua
+++ b/undo.lua
@@ -1,8 +1,7 @@
 -- undo/redo by managing the sequence of events in the current session
 -- based on https://github.com/akkartik/mu1/blob/master/edit/012-editor-undo.mu
 
--- 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.
+-- makes a copy of lines on every single keystroke; will be inefficient with really long lines.
 -- TODO: highlight stuff inserted by any undo/redo operation
 -- TODO: coalesce multiple similar operations