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.
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".
I use VsVim on my native Surface Pro 3 OS and on a VM on my Mac both using Windows 10. I recently got a job where we use an AWS WorkSpace that is running Windows Server 2008 R2 and now I'm unable to use VsVim flawlessly (yy and dd both throw an exception for VS and halt the program for a second. Like a lag). All 3 instances are using VS 2015.
I've tried re-installing and recovering VS multiple times to make this work but still same issue. I guess my question is: is Windows Server 2008 R2 supported for this, the greatest of all VS extensions?
That's definitely supported. I actually do most of my own development on Windows server so that' shouldn't be the issue.
Curious: do you have a different vimrc on that machine? It's possible that VsVim is getting hung up on an entry there.
Tools -> Options -> Environment -> Fonts and Colors
Choose *Text Editor* in the "Show Settings For" box
Then, scroll down towards the bottom in the "Display Items" window until you find "VsVim Command Margin". By changing the foreground and background colors, you can change the bar (background) and the color of text in the bar (foreground) to better match your theme