about summary refs log tree commit diff stats
path: root/README.md
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2022-06-02 15:45:25 -0700
committerKartik K. Agaram <vc@akkartik.com>2022-06-02 15:45:25 -0700
commit670886240f78314b9925e94e1814a8ade5fbaf3e (patch)
tree9e52827ab930246aa88576007903a0fa11dbafb7 /README.md
parenta9a133e6fb80460ab364e66206a7ffc8f9404b46 (diff)
downloadview.love-670886240f78314b9925e94e1814a8ade5fbaf3e.tar.gz
after much struggle, a brute-force undo
Incredibly inefficient, but I don't yet know how to efficiently encode
undo mutations that can span multiple lines.

There seems to be one bug related to creating new drawings; they're not
spawning events and undoing past drawing creation has some weird
artifacts. Redo seems to consistently work, though.
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/README.md b/README.md
index 68999f3..871379d 100644
--- a/README.md
+++ b/README.md
@@ -6,6 +6,10 @@ 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.
+
 * The text cursor will always stay on the screen. This can have some strange
   implications: