Vim control mode

[drewcassidy]

Is there any possibility of a Vim style control mode in the future? The extensions API doesnt appear to be flexible enough for this, so it probably needs to be added as an official feature of the app

[serkanyersen]

In the roadmap it says they will add this feature soon https://github.com/Microsoft/vscode/wiki/Roadmap#theme-highly-demanded-features

[joaomoreno]

@jpoon

[jpoon]

We're making pretty good progress on a VIM extension over here: https://github.com/VSCodeVim/Vim. Feel free to stop by and leave a PR 😄

[serkanyersen]

Awesome!

[tmandry]

In implementing this, consider actually integrating neovim as a library instead of (inevitably) a perpetually incomplete clone. It's very stable, and developers will appreciate being able to bring their vimrc and plugins!

[jpoon]

Definitely! We have a similar discussion going on here: VSCodeVim/Vim#18. From my brief reading, it looks like we'll also need to install neovim as well; it might be too much to ask of vscodevim consumers to install neovim as I doubt VSCode will allow extensions to install random executables.

In any case, neovim looks promising. I haven't played with it too much so feel free to send any pointers on how we might get started.

[drewcassidy]

I feel like the VSCode extension API would need to be expanded significantly to properly implement vim, and looking at the project you appear to be having trouble with even the most basic aspects, like having a block cursor.

On Nov 20, 2015, at 4:00 PM, Jason Poon notifications@github.com wrote:

Definitely! We have a similar discussion going on here: VSCodeVim/Vim#18 VSCodeVim/Vim#18. From my brief reading, it looks like we'll also need to install neovim as well; it might be too much to ask of vscodevim consumers to install neovim as I doubt VSCode will allow extensions to install random executables.

In any case, neovim looks promising. I haven't played with it too much so feel free to send any pointers on how we might get started.

—
Reply to this email directly or view it on GitHub #300 (comment).

[ThatRendle]

@drewcassidy I actually came here to ask about a block cursor :)

Hopefully the now-open-source development of Code and its extensions API can be influenced by the requirements of third-party extensions.

[jpoon]

@markrendle, @drewcassidy: We now have a block cursor :)

@egamma: Maybe I'm missing something but I don't see this in the January Iteration Plan? To better understand the VS Code roadmap, the goal is still to expand the extension APIs to better support VIM (as an extension)?

I think most of the issues that we [https://github.com/VSCodeVim/Vim] have been struggling with have been localization -- dealing with the variety of keyboards/keybindings that I did not know existed

[egamma]

@jpoon To support a VIM extension is still on our roadmap. It was a temporary copy/paste incident that the above link was created and that this showed up on the January plan, sorry about that.

Regarding open issues in vscode to support a VIM extension is this list representative of the issues you are facing?

[jpoon]

It's fantastic that there is a VIM label. A couple more:

• Extension APIs: suggest window is displayed despite not having any suggestions #997
• alt-gr meta key not available? #1066

[alexdima]

Please see https://github.com/alexandrudima/vscode-vim if you are authoring a vim emulation extension for VS Code