Grant Mathews

Yes, definitely. That won't actually solve the problem in this issue however. Fixing this issue would essentially be a search and replace to replace "trigger a vscodevim undo step" with...

There are a fair amount of times where we use our undo history for something that vscode can't give us trivially. The biggest one that comes to mind is definitely...

sick!

I'm gonna close this as although it's true that we don't support .vimrc, I believe our settings.json support is a solid equivalent, except better because it has autocomplete and documentation...

I see your argument. Reopening this issue.

It's certainly on my radar, however it is currently deprioritized because: * There are a lot of other issues with more thumbs up that we need to get to first....

@polunzh The update is the post I made 9 days ago right above you. :P If you're curious, we pretty much tackle issues in this order: https://github.com/VSCodeVim/Vim/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc

Unlike our other highly upvoted issues which are difficult due to VSCode API limitations, this one is completely doable. Even without much experience in the codebase, someone could take a...

@rebornix we use PositionDiffs now. We have a "beginning of line" position diff that just tells the cursor to go to the beginning of the line after the transformation is...

Had the same problem. This is what fixed it: `npm install https://github.com/ddopson/node-segfault-handler.git` `cd node_modules/segfault-handler` `node-gyp rebuild`