VsVim

Free

VIM emulation layer for Visual Studio

(214) Review
Visual Studio
2015, 2013, 2012, 2010
Download (246,654)
2/22/2015
1.8.0.0
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (214)
Q and A (218)
Sign in to write a review
Sort by:

by Justin Domingue | May 15 2015

by FlyingToaster | May 14 2015

Really, truly great, and always improving!

by NPS_Nat | May 13 2015

I use this plugin every single day at work. So happy I can use vim with VS. Very solid.

by CepsPrin | May 03 2015

Great extension, best part is it reads your vimrc file and works with your custom keys, excellent!

by _sotomo_ | April 29 2015

As someone who'd like to learn more about VIM, I'm finding this to be both a useful and educational way to get started. If you are new to VIM, I'd recommend checking out the "VIM Tutor" text file.

by pjwhams | April 17 2015

Massively useful. The very first extension I install

by Yiheng Tao | March 31 2015

Must have :)

by Andy Yong | March 30 2015

This is a must have for any VIM user. Integrate nicely with VS.

by mboren | February 26 2015

This extension is phenomenal. It implements a lot more than I would have expected.

by Eduardo A. C. de Sousa | February 26 2015

Great extension! Can't live without it anymore.

by Ammar.Zaied | February 13 2015

good job, thanks.

by TrevD1 | February 12 2015

Great plugin, thanks! Includes a lot of vim functionality!

by keith0930 | February 10 2015

by v-yadli | February 07 2015

Been using this for years. Rock solid and feature-rich.

by Ryan Manwiller | February 02 2015

A great vi plugin for visual studio!

by CurtisP | January 28 2015

by why666 | January 22 2015

Brilliant. Finally something that stops my getting abused with compilation errors complaining about the "ZZ"s I leave around the code.

The only thing I truly miss is compatible mode for undo. I've been using vi for that long I use "uu" a lot to get me back to my last edit. Whereas nowadays I lose my last two edits :-)

by Sema4718 | January 07 2015

by nitis | December 29 2014

by GeneG1 | December 27 2014

1 - 20 of 214 Items   
Sign in to start a discussion


  • REG 0
    3 Posts | Last post June 10, 2014
    • Typing in :reg 0 in command line gives this error:
                    Trailing characters
      
      Would you be able to support showing selected registers at once in the future like VIM does?
      For example:
                       :reg a b c
      
      Thanks.
      
    • Also,
      :reg " for the unnamed register shows the whole list, but should only show the " register. Typing in just :reg to show all registers works properly, I have the latest version installed, thanks.
      
    • Thanks for reporting the issue!
      
      Right now this feature isn't supported.  Only :reg without options is actually implemented.  The reason you are seeing the different behavior for :reg " is that the parser is interpreting " as a comment and hence just parsing out :reg by itself.  
      
      I filed the following issue to look into this
      
      https://github.com/jaredpar/VsVim/issues/1379
      
  • Support for inner tag block command?
    2 Posts | Last post June 03, 2014
    • It doesn't seem the "it" command works with VsVim (eg: "dit" to delete everything within an html tag).  I noticed it does work in sublime text's vim emulation.  It would be a much appreciated feature!  Great work btw, I love the plugin!
    • Support for "it" is being tracked by the following issue
      
      https://github.com/jaredpar/VsVim/issues/1094
      
      I'm hoping to get that into the next release of VsVim.  
  • Visual mode disappears when moving cursor
    2 Posts | Last post May 26, 2014
    • A lot of times the visual mode __shift + v__ disappears if I press (or keep pressing) hjkl or Ctrl+d (page up) or Ctrl+u (page down). This can get quite frustrating. If you can reproduce this bug, would appreciate a fix for this.
    • I've tried to reproduce this and I'm unable to do so.  Is there a particular file type or size that this reproduces on more often? 
  • Backspace not working in Insert Mode?
    2 Posts | Last post May 26, 2014
    • Hitting the <backspace> button on the keyboard whilst in INSERT mode does not delete the character.
      
      Any help would be appreciated.
      Thanks.
    • Sorry you're having an issue.  The most likely cause of this is VsVim is picking up your _vimrc and it has an insert mode mapping for the <BS> key that VsVim can't handle.  The easiest way to test this is to run :imap and see if the <BS> key is mapped.  If so the quick fix is to run :imapc
      
      Long term the fix is to add a _vsvimrc file in the same location as your _vimrc file.  VsVim will prefer this file and hence not read in the mapping. 
  • <C-r> No longer works in the commandline
    2 Posts | Last post May 22, 2014
    • <C-r> still works in the document as redo, but it no longer works in the commandline. Before I realized <C-r><C-w> wasn't implemented, I tried to use it. <C-r> kept giving me a cursor in the text, but I was unable to yank and paste a whole word as intended. I tried it repeatedly and in the process somehow managed to completely disable <C-r>. Now, <C-r> does almost nothing and I can't even paste from a register into the commandline. It does insert an invisible, width-less character into the commandline, but this has no effect that I've noticed.
      
      I tried uninstalling and reinstalling VsVim, but that had no effect, likely due to residual settings files from the original install. I tried reassigning <C-r> to Visual Studio and then back to VsVIM in the options, but that hasn't helped either.
      
      Help welcome.
    • Right now <C-R> is not implemented for the command line editor.  I have the following issue tracking getting it implemented
      
      https://github.com/jaredpar/VsVim/issues/1252
  • Highlighting/visual mode disabled after update?
    3 Posts | Last post May 06, 2014
    • Updated a bunch of stuff recently and now highlighting a section with mouse and hitting (eg) 'x' no longer cuts that selection to buffer, but rather inserts an 'x' where selection was. This happens irrespective of whether I was in insert mode or not when selecting started, if that makes a difference. Did a setting get overwritten somewhere? 
      
      Thanks for the great plugin, it's a lifesaver. 
    • It looks like you are running into a settings change that occurred in the latest version.  The default settings moved to gVim 7.4 vs. the old 7.3.  Here is a thread detailing how to get back the old behavior
      
      https://github.com/jaredpar/VsVim/issues/1322#issuecomment-37835924
      
      In the next version of VsVim it's going to be a nice GUI option instead of a vimrc solution 
    • That's exactly what it was, thanks. 
  • Strange behavior in .ts
    3 Posts | Last post April 23, 2014
    • The behavior described here:
      "Latest vsVim in VS2013.
      I have this line in a .cshtml file:
         @Html.ActionLink("CM Demo", "Index", "CM", null, new { @class = "navbar-brand" })
      
      Editor is in normal mode.
      If the cursor is in one of the quoted strings ("CM", for example).
      When I use this command:
      :wa
      I end up with this, editor is in insert mode:
         @Html.ActionLink("CM Demo", "Index", "C" +
                                               "M", null, new { @class = "navbar-brand" })
      
      Strange."
      
      This behavior is happening in .ts files as well now.  It's pretty annoying, because often when I go save, it just adds a line instead.  BTW I started noticing it after I installed resharper.
    • Btw thank you for the awesome plugin :)
    • Thanks for reporting the issue!  I've already done a similar work around for this R# feature in C# files.  Looks like i need to add support to other file types as well.  
  • VsVim is so cool.
    4 Posts | Last post April 23, 2014
    • Click esc will change to command mode twice. (keydown, keyup)
      This is bothering me.
      Sorry for my sorry English.
    • Can you try explaining a bit more what is going on here?  It's unclear what is going wrong.  Can you go through the key sequence you execute and exactly what VsVim is doing incorrcectly? 
    • I saw:
      The Escape key was pressed and we are still inside of Insert mode.  This means that Visual Assist handled the key stroke to dismiss intellisense.  Leave insert mode now to complete the operation.
      
      I often press key like this : Esc↓ o↓ o↑ Esc↑. It's different from Vim.
      Maybe I'm the only one press like this.
      
    • What version of VsVim were you seeing this behavior with?  The most recent version should fix this bug.  I added some work arounds to ensure that insert mode is exitted when Esc is pressed even if Visual Assist uses it to dismiss intellisense 
  • Disable alert sound?
    2 Posts | Last post April 21, 2014
    • Hello Jared,
      
      When using VS Vim, if you move the caret to any extreme position of the document, and you try to move the caret beyond what you can, the plugin produces an annoying alert sound, for each key you type that is invalid.
      
      It is actually OK when I'm using it in my Office (no speakers), but when I have my head set, I actually hear it all the time.
      
      Could it be possible to disable it or provide an option to do so?
      
      Many thanks :)
      Denis
    • This can be turned off by typing the following
      
          :set vb=
      
      This unsets the "visualbell" option that disables all beeps 
  • Block caret renders over quick find pop-up window
    2 Posts | Last post April 12, 2014
    • Hi Jared,
      
      In previous versions you could not use normal mode commands when the Quick Find pop-up window was active. In 1.6.0.2 you can and this is very useful! However, there seems to be a bug in the drawing code. 
      
      If you have the block caret over text in the top-right area where the pop-up window appears, pressing Ctrl+F will show the pop-up window but the block caret keeps being drawn over the pop-up window's screen area instead of being clipped out since it should be "behind" the pop-up window (the regular I-beam caret is properly clipped out in insert mode, as is the text in both normal/insert modes).
      
      Hope I explained that properly!
      
      Thanks,
      Eric.
    • Sorry, thought I had responded to this a few days ago but noticed when answering a diff question that i had not.  
      
      Thanks for pointing that out.  It looks like my adornment is somehow beating out the find adornment and hence layering on top of it.  I'm looking into how to resolve that
31 - 40 of 218 Items