I'm an avid tmux+neovim user, too, though working with Reason is a lot easier in VS Code. Making the switch from actual vim to fake vim (ie JS emulation) sucks.
Recently, VSCodeVim merged #1725 to add actual neovim as an editor - it's using NeoVim's embedding API so you're using neovim to edit the text file inside of VSCode's chrome, including all of VSCode's type hints and popups. Info here: https://github.com/VSCodeVim/Vim/issues/1735
I'm really stoked that we get the best of both - for languages with first-class VSCode support we don't have to decide between a half-baked VIM plugin or using VSCode without vim... you get both!
To be clear (as the guy behind these efforts), what was merged was a PR to let Neovim handle Ex-commands. This by itself was already pretty cool. In <200 lines of code, we were able to obtain full Ex-mode support, an aspect that had already taken 2000+ lines of code for much more limited support.
The PR for full neovim integration is the one you linked. It's more than just making it work with your existing .vimrc file: it's making it work with most vim plugins, leveraging the neovim runtime to make macros run faster, etc.
FWIW, in all the times I've tried to use Emacs with Evil, it's still not been quite good enough. Enough friction here and there to bring me to a dead halt and make me reach for vim again.
same with me. tried everything to use evil with emacs (since i really wanted to use orgmode), but it's just not the same. the emacs keybinds get in the way of vim mode imho.
You definitely need to add a bunch of extra emacs configuration on top of the standard evil-mode stuff to get a fully intergrated emacs<->vim environment. On top of that, for most meta modes (e.g. dired, magit) you'll have to either find an evil-compat set of bindings, write your own, or get used to the emacs way of doing things in these special buffers.
Spacemancs is another half-step up the ladder toward OS. It's a bunch of configuration utils and conventions that other people have decided for you--which may or may not be what you want.
I actually have moved from VIM (I had an Amiga that I learned Vim on) to VS Code. The Vim plugin is just great but the VS Code ecosystem id great and when I switched was much fast than Atom. If people can look past their Electron Bias they might actually find a great open source tool.
This is great. Just enabled it and it's really nice having a full version of vim inside of vscode. I actually switched from vscode to atom a while back because the vim emulation in it was a little bit better, but I'm definitely going to switch back because of this. Thanks again for the heads up :)
Recently, VSCodeVim merged #1725 to add actual neovim as an editor - it's using NeoVim's embedding API so you're using neovim to edit the text file inside of VSCode's chrome, including all of VSCode's type hints and popups. Info here: https://github.com/VSCodeVim/Vim/issues/1735
There's an ongoing rewrite to make neovim also work with your existing .vimrc file: https://github.com/VSCodeVim/Vim/pull/1897
I'm really stoked that we get the best of both - for languages with first-class VSCode support we don't have to decide between a half-baked VIM plugin or using VSCode without vim... you get both!