From 4f76ea37d7a24e6562fb8640935750c50de62e69 Mon Sep 17 00:00:00 2001 From: "Kartik K. Agaram" Date: Thu, 2 Jun 2022 17:46:30 -0700 Subject: more efficient undo/redo Now the bottleneck shifts to applying undo/redo in large files. But things should be snappy if you don't use the sluggish feature. --- README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 871379d..7eb3a5e 100644 --- a/README.md +++ b/README.md @@ -6,9 +6,8 @@ http://akkartik.name/lines.html * No support yet for Unicode graphemes spanning multiple codepoints. -* Undo is extremely inefficient in space. While this app is extremely unlikely - to lose the current state of a file at any moment, undo history is volatile - and should be considered unstable. +* Undo/redo can be sluggish in large files. If things get sluggish, killing + the process can lose data. * The text cursor will always stay on the screen. This can have some strange implications: -- cgit 1.4.1-2-gfad0