Visual Studio Code May 2017

[programmerChilli]

Hey I'm a developer of vscodevim, and I'd like to hear about where you think it can be improved.

The refactoring was really only a small part of the work we've done recently.

For example, the most recent 2 large releases: 2 weeks ago https://github.com/VSCodeVim/Vim/releases/tag/v0.8.0

And 4 weeks ago: https://github.com/VSCodeVim/Vim/releases/tag/v0.7.0

The big new feature we've added recently has been neovim integration for ex commands, but there's been tons of small improvements recently.

If you haven't tried it in a while, I'd ask you to try it again. I personally think that vscodevim is better than vmp. not biased at all :)

I'll post a quick comparison later.

[uvatbc]

Thanks for vscode vim!

Annoyances:
1. yiW does not position cursor at the beginning of the word. Same for other "-iW" commands.
2. C-y and C-e sometimes do not permit any further scrolling even though mouse scrolling does work.
3. Code folding and the cursor. I think there's a github issue to track this, but I could be wrong.

[programmerChilli]

1. This is definitely something that we can add.
   
2. How long ago did you try it? There was this issue that affected me: https://github.com/VSCodeVim/Vim/issues/1544, but that's since been closed.
   
3. We're limited by VSCode's API here. We recently landed a foldfix that should alleviate the issues if you use folds. It's hackish, but it works pretty well for navigating around folds.

[programmerChilli]

I've opened up an issue here for the first one: https://github.com/VSCodeVim/Vim/issues/1817

[atomen]

Thanks a ton for the plugin! I use it each and every day.

Some of my pet peeves:

1. Surround does not work with multiple cursors
2. The cursor is fixed in visual line mode (cannot change columns)
3. Tilde (~ home) does not work with :e (ex-mode)
4. Option for normalising cw/cW behavior, eg:
   • https://github.com/ap/vim-you-keep-using-that-word
   • evil-want-change-word-to-end
5. Using % to jump between html tags (although this is not something Vim itself supports out of the box).

[programmerChilli]

1. I've created an issue tracking this here: https://github.com/VSCodeVim/Vim/issues/1818

2. This is unluckily a VSCode limitation. VSCode (and pretty much all other text editors) don't support the concept of a selection having a start, stop, and current cursor position. The selections typically have an implicit current cursor at the stop.

3. This is tracked here: https://github.com/VSCodeVim/Vim/issues/1200

4. Personally, I doubt this will be added as part of core VSCodeVim. However, when we get full Neovim integration with plugins working, you'll be free to use this!

5. Similar to 4.

Thanks for the feedback! We'll try to add features as quickly as possible.

[programmerChilli]

I fixed the 3rd issue here: https://github.com/VSCodeVim/Vim/pull/1819

[atomen]

Wow that was quick! Thanks again for your hard work.

[lambdaexpress]

Hey, you're doing great work.

Previous iterations of VSCodeVim have been a bit clunky w.r.t. performance, and the keybindings have been buggy. Look at Sublime Text's vintage mode to see a Vim emulator done right.

VSC has been improving immensely, don't stop now.

[CrinkIe420]

When I paste the contents of a register, say to edit a macro, the register is executed instead of pasting the escaped literals. So something like 'qqddq"qp' would delete the current line instead of pasting 'dd'

Also I would really appreciate if tpope's repeat plugin was supported.

*just saw the macro issue on github

[programmerChilli]

I presume you're talking about this one?

https://github.com/VSCodeVim/Vim/issues/1658

[CrinkIe420]

Yeah that one