2 ms·
One of the most annoying thing with this extension is that it maintain a different revert history that is conflicting with the normal one. Sometimes you just ha
by speedgoose 7y ago
One of the most annoying thing with this extension is that it maintain a different revert history that is conflicting with the normal one. Sometimes you just have to close a file without saving it because undo/redo is broken.
And it's extremely slow on medium to large files and it gets slower and slower until you restart vscode.
I have a love hate relationship with this extension. It's terrible but vscode without it feels worse to me. Sometimes I wish I didn't met vi in my life.
- Epskampie 7y agoHeh, that’s how I feel after reading this article. I don’t use vim a lot, haven’t gotten used to it. It must be so frustrating always having to chase that “vim experience” in every editor, but never quite getting it.
- shhsshs 7y agoI’ve kind of learned how to juggle the two disconnected undo buffers in my mind. If I want to just go “back in time”, repeating even my previous undo/redos, I use Ctrl-Z. To undo a quick mistake I use Vim’s undo. I guess I treat them like short-term and long-term “undo” actions. Sounds kind of weird now that I’ve put it in writing. It works for me but YMMV.