This gives Visual Studio the interface it deserves. It is worth the install for macros alone. I discovered this today after attempting to use the official macro tool from Microsoft. I tried maybe 15 times to do a simple macro converting a standard If,Then,Else,End If construct into the equivalent ternary construct, but every time my result would be wrong in a different way. Even if that weren't the case, the lack of vim's text navigation language made the entire process very clunky and inefficient.
I didn't even bother to look up how to turn off IntelliSense for macros (and I imagine it would be impossible, or require manually disabling it every time). Thank the coding gods I decided to search for vim emulation. The last time I checked there was only a paid option for this (although that one could also work in word/excel/etc).
Simply fantastic, this was the plugin that actually made it feasible for me to learn Vim while still remaining productive, and my editing has been made easier and quicker by it; I almost never have to use the mouse. The navigation features (combined with Visual Studio's Ctrl-,) makes for a pretty good workflow. Thanks so much for your work, VsVim (and Vim) is fantastic.
This is something that used to work ok (a couple of months ago), and so I wonder if it's the latest VsVim, or VS 2015 update 3 (or the interaction of the two) that broke it.
- Type Shift-End
EXPECTED: the line is selected, up to and including the last character
ACTUAL: the selection stops on the last character. You have to press Shift-End again to extend right to the end.
If I disable VsVim then this behaves as expected in VS. This issue causes problems with VisualAssist and other extensions that manipulate the selection.
Can you reproduce, or is it some other problem with my setup?
When editing a condition breakpoint, the period key is passed to the underlying buffer and performs the last VI command.
Eg: When typing this condition in the popup: 10005 == serverInfo.m_id
the period in the type is not captured by the breakpoint condition window and is instead passed to the document deleting a line (the last VIM command I ran).
I'm using VsVim v18.104.22.168 with VisualAssist v10.9.2108 in VS2015 sp3.
Hi Jared....Total vim newb so here comes a stupid question....is there any way to integrate vim plugins into vs vim? vim-seek, vim-sneak, evil-snipe seem pretty sweet. Or maybe there is a way to do it in vs vim. Anywho, really enjoy using vs vim. Thanks.
Unfortunately no. Full Vim Script support is not a goal of VsVim and as a result plugins won't work. I've looked at doing it a few times and the cost is very high and it's not really possible to be compatible enough for plugins (due to limitations in Visual Studio). Hence it's not on the feature list.
If i want to map a key to start debugging, what should i do?
I tried :
:nmap ;d Debug.Start
It only shows parse error.
I bind <F5> to start debugging using Options-keyboard, then tried :
:nmap ;d <F5>
but still failed.
Whenever I press "/" to do a search within a document and I want to paste from the contents of the clipboard, I have to explicitly click in the command box to paste to it. How do I get this to work the way I would expect it to work on a terminal, that is for the paste to hit the command box instead of the editor?
In some vsvimrc's I find that people have bound keys to commands such as
Debug.ExceptionSettings, View.FindResults1, View.FullScreen, Team.Git.GoToGitChanges, etc.
How can I find the vsc command equivalent of a Visual Studio command?
Try grabbing the latest build from here. It will work with Atmel 7. I'm going to do the official release that works next weekend.
I ran the build you linked to and the plugin installed successfully to atmel studio 6.2 but not 7.0. When I ran it a second time I get the message "The extension is installed on all available products".