I follow ur methods tried, but did not play a role.It's useful in VS2013,but in 2015 does not work.Could u please try to sovle it?
By the way, do you know what the font is in this comment area? it is very good.
There is a bug in VS 2015 that prevents this from working. It should be fixed in the next public release.
It appears the font is monospace (at least that is what is showing up in Chrome developer tools).
A long and white status bar looks bad in VS2013 with dark theme, how can I change the background and text color of the status bar?
And, Visual Studio has its own status bar, why not just use the visual studio status bar instead of creating your own? I really want to save screen space as much as possible.
The color of the command margin can be changed in Tools -> Options -> VsVim under the Item Colors section. Both the foreground and background can be changed here.
The Visual Studio command bar just really isn't sufficient for the needs of Vim. At a high level it's meant for short term, non-editable, global status messages. Vim needs long term, editable, local command bar. There are other more technical reasons why I made this choice but at a high level that's the reason.
I have gotten enough requests for this though that VsVim does support using the status bar only. To enable that go to Tools -> Options -> VsVim and set "Use Editor Command Margin" to false.
Note: This is a brand new feature that I don't actively use myself. It probably still has several bugs that need to be ironed out. And long term it won't be as functional as the command margin (in particular it won't support edit). But overall it should serve as a reasonable substitute.
Thanks for the reply, I'm new to vim so I didn't really know what command margin means when I asked that question, sorry to bother you for that
But there is a minor problem that I hope you can help me solve:
I am a chinese, and like all other programmers in China or Japan and some other countries, we use input methods to input our language.
In insert mode, there is no problem.
In Normal mode, when I type 'i' for example, I meant to enter Insert mode, but if my input method is active, the input method will intercept my input, so I have to disable my input method and type again, this is a bit annoying.
Is there anything you can do from your end to disable input method (if enabled) temporarily when in Normal mode?
Sorry, make mistake.
This link is correct.
1. open Vs2013 and enable vsvim(Handle all with VisualStudio).
2. switch input from english to chinese. then vsvim will not work normal.
For example, Ctrl + j to list members, but in this situation, it will linefeed.
I can't find feature, which would let me to save the marks, when i close visual studio (2013).
That is, in one session of using VS, marks works fine, but when i close studio and open it again, marks is erased.
That feature isn't implemented right now. I've thought of saving marks and a few other items on close but just haven't seen a strong demand for the feature. It's something I will consider for a future release.
I've been debating making the jump from ViEmu to VsVim for better config support via vimrc (currently the only usable mapping that makes sense is 'nnoremap <esc> :noh<cr><esc>'), but I'm struggling with navigating between window splits. I've figured out splitting via command mode with :split and :vsplit but normal mode commands <C-w> s, <C-w> v, and <C-w> w do not work. I haven't found a way to move between horizontal splits without using the mouse, and I can't navigate between vertical splits at all without using <C-tab>.
Using ViEmu, I'm used to gt and gT taking me to the next buffer, regardless of tab well, though I appreciate the difference in VsVim where every open tab is treated as an open buffer, there's no indexed buffer list (:ls) so I can't jump to a given buffer (:b1 :b2 etc) without cycling through every open tab. I'm also unable to open a new buffer (:e SomeFile.cs) which keeps me reliant on the solution explorer search.
I feel like I'm missing something fairly major, but I've searched and all the ways of splitting and navigating splits and buffers doesn't seem to be supported outside of :split and :vsplit
As for the <Ctrl-W> commands I just wasn't aware of them. I've been using the :split and :vsplit commands for as long as I can remember and had never seen this alternative. It's fairly easy to implement and I filed the following issue to track getting the work done
As for the buffer list. Vim and Visual Studio unfortunately have a very different understanding of how buffers work. A couple of times I've tried to map out how the buffer commands should work in the world of Visual Studio but I've been unable to convince myself of a model that made a ton of sense. If you have any ideas here I'd love to hear them.
For :e the command is implemented today but has no sense of relative path. How are you expecting the path to be resolved here? Relative to the current project, solution, etc ...?
As far as a buffer list goes, it would be nice just to use :ls to get a numbered list of files that are open, you don't necessarily need to treat a vertical split of the same file as separate buffers. gt and gT would cycle numerically through the buffers forwards and backwards (alternate commands are :bn and :bp), as well as :b n to jump to buffer n. The ordering of that list is entirely up to implementation I suppose. Tab order is the initial thought, but multiple windows, screens, and tab wells complicate things. If VS has a way to progressively iterate through those by level (window, well, tab) that I guess would be the simplest way to go, since "order opened" doesn't make sense when opening a project with files already open. ViEmu only places a file in the list if you've made changes to it during that session or it was the first file with focus, but then you have to :e FileThatIsAlreadyOpen.cs to be able to jump to it. It's not the worst idea, I suppose.
for :e, I just tried using it and even from a file in the same folder I get "The document cannot be opened. It has been renamed, deleted or moved." I'm used to typing :e fileiwant.cs non-case sensitive regardless of path, sort of like a quick find, though I don't have many projects where the same file exists in multiple paths so I never thought about the particulars of path relevance. If one were to build in path relevance if path is specified, it should probably be from the solution root.
Unfortunately VsVim does not support vim style plugins. VsVim does have some support for the vim script language but not nearly enough to support extensions.
There are a number of alignment extensions out there for Visual Studio which may help you
I'm not sure if they target VBA or not though.
First, thank you for the app. Excellent work.
I frequently use :g/re/p to print all the lines in a file matching /re/. I am getting the following when I do so:
Undo linked chain broken. Falling back to Visual Studio undo
Is this a configuration conflict or a bug?
Thanks for your help with this,
Thanks for reporting this!
This is a bug. In the most recent release I fixed a number of undo / redo bugs in VsVim and really tightened the diagnostics around it. What you are seeing here is a place where the tightened diagnostics are incorrectly firing. I just uploaded a fix for this bug and it will appear in the next release
I had read the faq and when I type :set in Visual studio, I get the below.
The following is what I have in "C:\Users\allai\_vimrc",
I tried different things.
2) set shiftwidth=5
Seems to have no effect to visual studio.
Any idea What I am missing?
I want to reconfigure the key bindings, but I can't find the option button that you mentioned it would be located in the right-bottom in editor windows.
I'm using visual studio 2013 professional. How can I reconfigure the key bindings or find option button?
In recent versions the Options button has moved to the Visual Studio Options menu. Go to Tools -> Options and navigate to VsVim in the dialog that pops up. The old menu is in that section under Keyboard
I have been using vim on windows for a while and have a good setup. Doing some VisualStudio work and VsVim has been working great for me. I have discovered a few plugins and keybindigs simple do not work, and reading through the notes found that they are not supported. That's fine, but I still want them for normal vim.
Is there a way to exclude some vimrc lines from execution is VsVim? I searched the docs and could not find anything. I have exclusions for different OSs. I was hoping there was an env variable I could use to exclude a few items.
Thanks for the help,
One approach is to have a separate vimrc file for VsVim. If u have a file named _vimrc then VsVim will prefer that over a standard _vimrc. This is what I do.
I have thought about adding a VsVim variable for use in an 'if' block jn the rc file. This will very likely happen for a future release but isn't implemented yet.