persistent undo
See original GitHub issueWould be great to have this in VS Code.
I enjoy in plain (neo)vim when I’ve set my undo path and have and
if has('persistent_undo')
set undofile " keep an undo file (undo changes after closing)
endif
so that every time I re-open a file any time in the future (even after closing vim/neovim) the undo history persists.
I have that setting in my init.vim
, but looks like it doesn’t work in VS Code Neo Vim.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Using Vim's persistent undo? - Stack Overflow
One of the new features in Vim 7.3 is 'persistent undo', which allows for the undotree to be saved to a file when...
Read more >Persistent Undo in Vim - - Jovica Ilic
Vim supports persistent undo, which means that you can run undo/redo even from your previous sessions. Persistent Unto in Vim.
Read more >Use Persistent Undo in Vim for maximum comfort
Intro to the benefits of persistent undo functionality for Vim-centered development workflows. ... From version 7.3, Vim supports persistent undo.
Read more >Persistent undo and repeat | Mastering Vim - Packt Subscription
Persistent undo and repeat. Like any editor, Vim keeps track of every operation. Press u to undo a last operation, and Ctrl +...
Read more >Learn how to use vim undo to time travel - DEV Community
Persistent undo. When you close a text editor, normally you lose all your undo history. This means when you open that file again,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Can we arbitrarily replace a neovim buffer’s undo history? (basically the other way around).
If so, then that may be a way to rely on VS Code’s semi-persistent undo (and eventually its fully-persistent undo), although in this case we would lose the history tree. But it could still be a worthy option for those that are okay with not having the tree.
EDIT: Oh, but we would need to read VS Code’s history stack, which may not be possible.
The problem is that the vscode undo stack isn’t loaded back into the neovim buffer, so unless you use the vscode undo functionality, it won’t work.
On Wed., Dec. 30, 2020, 1:40 a.m. David, notifications@github.com wrote: