Resolving the great undo-redo quandary
github.com
Resolving the great undo-redo quandary
1–10 of 247 posts
Re: Resolving the great undo-redo quandary
#2Sounds similar to vim’s time travel command
:earlier 30m
Re: Resolving the great undo-redo quandary
#3Would be useful if this had a comparison with Emacs, which also resolves the GURQ.
Re: Resolving the great undo-redo quandary
#4This is exactly how undo works in Emacs out of the box. Personally, I prefer to install the undo-tree package and manually browse through the tree of undo paths. I'm not sure why this author finds a tree unacceptable for this purpose.
Re: Resolving the great undo-redo quandary
#5The !Edit text editor in RISC OS used this algorithm in the late 80s. https://www.databasesandlife.com/risc-os-edit-undo/
I must admit I found it a bit confusing at first. Took me quite a while to form a mental model of how it worked.
Re: Resolving the great undo-redo quandary
#6I implemented something similar for a interactive whiteboard project once. The undo operation would simply be appended as another action that itself could be undone by re-doing it.
However, as you played with it, it became confusing because it ran counter to ingrained expected behavior of an undo/redo dual stack implementation. Eventually I implemented the classic approach.
Re: Resolving the great undo-redo quandary
#7> No, there is no undo "tree"[...]
This is still a tree, it's just implemented in an array.
Re: Resolving the great undo-redo quandary
#8Sounds like the Braid version of undo-redo.
Re: Resolving the great undo-redo quandary
#9This is exactly how undo works in Emacs out of the box. Personally, I prefer to install the undo-tree package and manually browse through the tree of undo paths. I'm not sure why this author finds a tree unacceptable for this purpose.
Because it requires more than two commands
Re: Resolving the great undo-redo quandary
#10Alternatively, use Vim undotree: