Show HN: Text undo that doesn't lose your edit history vladimirslepnev.me 11 points by cousin_it 3 days ago
leephillips 3 days ago This is built in to vim. Bjartr 2 days ago For those interested, here's the Vim docs for the undo treehttps://vimdoc.sourceforge.net/htmldoc/usr_32.html cousin_it 2 days ago My approach was linear, not a tree. The innovation (a small one) is how to make linear actually feel kinda ok, but at the same time not lose work. leephillips 2 days ago If I understand correctly, the vim undo tree is a superset of your approach: in vim you can go forward and backward in time, seeing all versions of the file, and need not explicitly deal with the tree.
Bjartr 2 days ago For those interested, here's the Vim docs for the undo treehttps://vimdoc.sourceforge.net/htmldoc/usr_32.html cousin_it 2 days ago My approach was linear, not a tree. The innovation (a small one) is how to make linear actually feel kinda ok, but at the same time not lose work. leephillips 2 days ago If I understand correctly, the vim undo tree is a superset of your approach: in vim you can go forward and backward in time, seeing all versions of the file, and need not explicitly deal with the tree.
cousin_it 2 days ago My approach was linear, not a tree. The innovation (a small one) is how to make linear actually feel kinda ok, but at the same time not lose work. leephillips 2 days ago If I understand correctly, the vim undo tree is a superset of your approach: in vim you can go forward and backward in time, seeing all versions of the file, and need not explicitly deal with the tree.
leephillips 2 days ago If I understand correctly, the vim undo tree is a superset of your approach: in vim you can go forward and backward in time, seeing all versions of the file, and need not explicitly deal with the tree.
This is built in to vim.
For those interested, here's the Vim docs for the undo tree
https://vimdoc.sourceforge.net/htmldoc/usr_32.html
My approach was linear, not a tree. The innovation (a small one) is how to make linear actually feel kinda ok, but at the same time not lose work.
If I understand correctly, the vim undo tree is a superset of your approach: in vim you can go forward and backward in time, seeing all versions of the file, and need not explicitly deal with the tree.