[braindongle]

Let us not disparage VSCodeVim in the least. #1: .vimrc support. Simply huge. Not everything is there, but a lot is.

Also, they are responsive. The big outstanding thing for me is Code's behavior with respect to opening a new file/buffer. Tabs are owned by splits whereas it's the other way around in Vim, and that's fine, but the Vim default of replacing the active file/buffer must be!

I figured out a workaround [0] just this week with a little help, but more importantly, after suggesting that this feature make it into the extension, I received a prompt reply [1]. These people are doing great work that really matters for me professionally.

Good luck implementing the 8,000,000 Vim features that you use and don't even think about by starting with nothing but a context for mode-switching.

[0] https://stackoverflow.com/questions/60216168/vscode-open-fil...

[1] https://github.com/VSCodeVim/Vim/issues/4559

[city41]

I don't mean to disparage it. Apologies if my post came off that way. I certainly appreciate it and understand emulating vim is not an easy task.

[braindongle]

Yeah, I was thinking I may have been a bit aggro there. It's just a coincidence that I only recently embraced IDE life (finally!), and it's in no small part because of this extension. Cheers.

[city41]

No, I appreciate the call out. My intention wasn't to be negative, but I really was in retrospect. I will be more mindful in the future.