diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2022-06-02 17:46:30 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2022-06-02 17:46:30 -0700 |
| commit | 4f76ea37d7a24e6562fb8640935750c50de62e69 (patch) | |
| tree | a067abd0be2cf6dffcecf231873ace189d62a061 /README.md | |
| parent | 22817492a3c5dd33c7d34c0c505b2bac2661d0ac (diff) | |
| download | view.love-4f76ea37d7a24e6562fb8640935750c50de62e69.tar.gz | |
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.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 5 |
1 files changed, 2 insertions, 3 deletions
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: |