2 ms·
> In VS Code, it maintains its own undo stack, and the interactions between the two undo stacks are terrible and terribly frustrating That’s because Vim has a
by Lio 2y ago
> In VS Code, it maintains its own undo stack, and the interactions between the two undo stacks are terrible and terribly frustrating
That’s because Vim has a more sophisticated undo stack than VS Code.
Vim keeps its history as a tree where you can jump between branches.
- chrismorgan 2y agoIt’s not about stack versus tree; it’s about the granularity of changes and what causes actions to be pushed to the undo stack (where there’s a pretty fundamental difference between modal and non-modal editors), and the fact that I suppose VS Code just doesn’t let extensions directly manipulate the undo stack in the way required. Look through https://github.com/VSCodeVim/Vim/issues?q=undo https://github.com/VSCodeVim/Vim/issues?q=undo, there’s a lot. VSCodeVim tries to make it behave more like Vim, and because it’s independent of the native undo stack, it’s frequently a miserable experience. Pretty sure I disabled it, when I tried using VS Code for a short while and with Vim mode.