Vi got under my skin 20+ years ago, and ever since, I find my fingertips are always itching to switch into vi mode, as it's the most intuitive way to edit code that I've encountered. So it was great to find this extension, and I'm impressed at how well such a minimal editor integrates into such a richly featured IDE. VS feels incomplete without it now . . .
This is always the first Visual Studio extension I install - could not imagine working in Visual Studio without it. VsVim is rock-solid and simply allows me to edit code more quickly.
For the uninitiated (or the Vi-traumatized):
1) It does not take comprehensive knowledge of Vi(m) commands to be much more productive with this extension (or Vi(m) generally). Basic Vi commands (http://www.cs.colostate.edu/helpdocs/vi.html) pack a lot of punch. 2) Yes, I am quite familiar with comparable Windows keyboard shortcuts for many things I do Vi-style using VsVim - and find myself seamlessly interleaving them with Vi(m) commands; TMTOWDI; but Vi is everywhere (including Visual Studio thanks to this awesome extension) and reduces reaches for my mouse and contortion on my keyboard more than anything else I have tried over 20+ years of nerdery.
Sure, maybe I am using the wrong name for the feature (its really just renaming, not refactoring). In VS, if you highlight (select) a variable name, on the declaration, and type over it with a new name, an icon appears that you can click on to open a menu that says "Rename <old name> to <new name>". Then if you click that, VS updates all of the references to this variable to the new name.
Also, you mentioned C#, which I haven't tried this in. I noticed this in VB, which is what most of the code I am working with is written in. This is not resharper or a similar plugin, as I do not have these for VS 2013 (still vanilla on that).
I don't have to do the renames that often, so I can work around for now by temporarily disabling the plugin and re-enabling when done, with VS restarts. I wouldn't do this for small local variables, but for properties, etc. of classes that are referenced multiple places, this might still be the quickest way, as a workaround.
Hi Jared, when you first type the d command the cursor in normal mode should go from a full block to a half block letting you know you pressed the key for the first part of a command, this currently works on the y and c commands perfectly and I thought before the upgrade this used to work. I'm using version 126.96.36.199.
Is there a hidden setting that makes this work like it used to?
I just checked and VsVim will use the half block on `d`. If it remains in a full block that typically means you have a normal mode mapping involving the `d` character (say :nmap da blah). In that case when you press `d` there is an ambiguity and VsVim correctly keeps it at full block
Eventually though the key mapping should time out in favor of the delete version of `d`. At that point VsVim should be redrawing the caret at half block. It is not though. I filed the following bug to fix that up
In gVim I can type 'ge' in normal mode to jump to the last character of the previous word, but for quite sometime now I can't get this to work in VsVim (using v188.8.131.52 with VS2012 Update 4).
Is this feature supported?
Great timing on the question. I just added support for 'ge' into the code base 2 days ago.
If you want to grab a build that has this feature you can do so from here
Consider the following text:
public SomeType MakeCopyFunc(SomeType 5)
If I place the cursor on the 'S' after public then type cwMyObjectType<esc> it will delete SomeType,and replace it with MyObjectType. This is good. But then I navigate to the 'S' after the '(', and hit the '.' key to repeat the last action, rather than replace SomeType with MyObject, it will replace it with _MyObjec .
Any idea what would cause this?
I can't quite figure out why it does it sometimes and not others. I will report back when I have it narrowed down.
That definitely shouldn't be happening. I have a lot of tests for this feature, many on very similar scenarios so I'm not sure why you are seeing that. If you are able to narrow this down please let me know
I don't know the vim well; however, I usually use the "shift+8" to find same keyword.
"N" is used to go next find result, and the "shift+N" is used to go previous result.Current version of VsVim is operated well for "shift+8" but there is no highlighting. Is it possible to highlight the keyword of the result of the "shift+8" ?
Right now you can do this by just using a Windows Paste operation (Ctrl+V). I have the following issue tracking getting Ctrl-R support into the command line editor
I downloaded the version from this site but the issue described here (https://github.com/jaredpar/VsVim/issues/1088) is causing me problems. Is it possible that a regression has been introduced since this bug was fixed?
No, there is no real equivalent for that in VsVim.
However that does look like a super interesting idea. I'm toying with the idea of just writing a stand alone EasyMotion plugin for Visual Studio. May try and do that later this afternoon as a fun project. Will post back here if I do.
Yeah, EasyMotion is incredible useful for navigating inside the current visible part of code. I can't live without it in gVim :)
If you have the time to code it a few things would be nice to have:
- Beeing able to set the keyboard shortcut for it (e.g. Ctrl+,)
- It would be nice if we can define the character range
By default it's normally "a-zA-Z0-9"
but I normally exclude 0-9 to make the keys easier to reach.
Thanks Jared for considering it!
I started working on it today and have the basic mechanics working at this point
Still needs a *ton* of polish, in particular getting the initial search bound to a key stroke rather than a menu item. Will probably get this posted by EOW unless I hit some kind of snag
Added a very early version of EasyMotion to the gallery. Still very much alpha / beta but can be played around with. Please let me know about any issues you find (probably quite a few)
Github (code + issues): https://github.com/jaredpar/EasyMotion
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
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!
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.
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.