VsVim

Not sure what I did, but when I compile I get several build errors saying "Unexpected character []" where the '[]' isn't to brackets but a closed box. I just didn't know how to reproduce it on my keyboard. Nothing like that shows up, but when I view the file in notepad++, it shows about 30 ACK control characters.

Were you able to see what the actual byte values for the control characters were?  If i can figure out what they are I have a better chance of figuring out why they're being incorrectly inserted.  

If you go to this link, it is number 6: http://www.cs.tut.fi/~jkorpela/chars/c0.html

I think what happened is I set all my shortcuts to be used by VsVim. I tried to do a Ctrl+F in my code but instead this was printed. Probably just a user error. I have since reset my shortcuts to be used by Visual Studio and Resharper. Is there any other way other than installation time to go in and selectively change which program gets which keyboard shortcuts? There was something in Tools > Options > Environment > Keyboard, but there was nothing related to VsVim in there. Thanks for the help!

Hi, Thanks for this really great extension. I am trying to be able to open files from the vim cmdline but it seems the path is always starting from system32 folder. I think it would be nice if the default path is same as the current opened file. It this supported?

Thank you

Thanks for reporting the issue

This is a known problem with the current version.  I'm working on changing this is future versions to be more like the vim behavior for paths.  Here is the issue that is tracking that bug

https://github.com/jaredpar/VsVim/issues/1039

Hi all, new to Windows and Visual Studio, coming from UNIX/Linux.

Just installed Visual Studio Express 2012 and glad I found Vim plugin.  I read posts that say it works on 2012 but fails when I install.  End of log is here:

26/02/2013 21:14:23 - Found installed product - Microsoft Visual Studio Express 2012 for Windows Desktop
26/02/2013 21:14:23 - Found installed product - Global Location
26/02/2013 21:14:23 - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
   at VSIXInstaller.App.InitializeInstall()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()

The Visual Studio Express SKUs don't support 3rd party extensions.  You need to have at least Visual Studio Professional in order to install extensions.  Unfortunately this is a policy decision by Microsoft and there is nothing I can do to work around it.  

That's a shame, thanks for the quick reply - I've been pulling my hair out!

Thanks for putting such a great editor together.

Is there a way to get :g/ working to show all lines of a pattern match?

I went ahead and created an issue to track adding :g/ to VsVim

https://github.com/jaredpar/VsVim/issues/1053

Hi there,

I've been using VsVim since almost the very beginning, and I absolutely love it.  There were some changes in the latest version that caused some frustration for me, and I thought I would share how I fixed the issues.

In the prior versions of VsVim, the "Show Line Numbers" Visual Studio Setting determined whether or not line numbers are displayed. This could be set on a per language basis.  VsVim now seems to override this setting - I determined this by disabling the VsVim extension.  To get line numbers back I added :set number in my vsvimrc file.  The new version seems to only look here when determining whether or not line numbers should be displayed, which has changed from older versions.

In the prior versions of VsVim, tab spacing settings where defined in the Visual Studio settings.  In this new version, my tab spacing seemed very erratic, which led me to believe that VsVim was overriding this behavior based on what was in the vsvimrc file.  By adding :set tabstop=4, I was able to stabilize the tab spacing problems I was having.

I hope this helps other people encountering the same issues.  Jared, perhaps you could confirm this new behavior and add some information to the FAQ?

Thanks,

Rob

Sorry this particular change caused you problems.  This was an intentional change in the behavior of VsVim though.  I wrote up a detailed discussion of why it happened here 

https://github.com/jaredpar/VsVim/wiki/Defaults-for-Settings

The shorter version though is: VsVim and Visual Studio share a group of settings (tabstop, line numbers, etc ...).  During start up these can differ from what comes out of _vimrc and what comes out of Visual Studio and VsVim has to pick a winner between the two.

The "pick a winner" process was never designed, it simply envolved and was hampered by decisions I made when VsVim was a private toy of mine.  Vs 2012 changed the way settings were loaded in a way that completely broke my implementation to the point where I had to make a breaking change of some kind.  After some thought I decided that if I had to break once I should do it correctly and use a design that would be maintainable for future versions as well. 

The new behavior is that if you have a _vimrc file then vim settings win.  Else Visual Studio settings will take precedence.  

After deploying this change and getting feedback from users I realized that some people want to both keep a _vimrc file but also want Visual Studio settings to win.  The next version of VsVim (to be released this weekend) includes an option to do that.  You can specify 

:set vsvim_useeditordefaults 

At which point VsVim will let Visual Studio win on every setting.  

Again, sorry this caused you grief.  

I'm so glad someone commented on the tab issue. I started using VsVim about a month ago and have been really enjoying it. Sometime last week I started noticing that auto-indenting and tab stops starting behaving strangely. For now I've removed my .vimrc file and that seems to fix the issue. Thanks Rob for pointing out your issue. A big thanks to Jared for a great tool that I really enjoy using.

Thanks for the response!  I should have searched around a bit more and I would have run across the posting you mentioned.

I noticed that if you navigate here: https://github.com/jaredpar/VsVim/wiki the page you mentioned isn't listed.  It only appears if you go here: https://github.com/jaredpar/VsVim/wiki/_pages.  I think that was my problem.  Perhaps you could put a link on the 'Home' tab for the wiki pointing to this new page?

Thanks again for the great software, it's really amazing and I can't imagine not being able to use Vim bindings when I develop.

Looking forward to your new release.

Rob

Yes you're correct.  I somehow forgot to link that on the main page.  i'll take care of that now. 

Glad you're enjoying it! 

The download limits my selection to my VS2010 Pro installation.
Is there something for VS2012 Express?

Unfortunately Visual Studio doesn't allow any 3rd party extensions for Visual Studio express.  There's nothing I can do about this limitation.  Extensions are only supported in Pro and above.  

Thanks for the response!

Is there a way to edit the command in VsVim command window? 
e.g. Suppose I started with :s/longsearchstringwithregexlikE\/.?*/replace and then want to edit this to :s/longsearchstringwithregexlike1\/.?*/replace is there way to edit my previous command. I am not able to  place cursor next to 'E' of search string using mouse and edit it.

Also is there a way to forward vsvim commands from VS command window?

There is no way to edit the command line commands in 1.3.3.  This feature is implemented and will be coming with 1.3.4.  I try to release on a monthly basis so hopefully this will be available in early march.  

At this time there is no way to execute Vim commands from the VS command window.  That is an interesting idea though.  I will look into it

Hi,

I am getting the following window when trying to install VsVim.
http://screencast.com/t/m0X5EPr8EHT
Even I see that Visual Studio 2012 is supported?

What can I do?

Visual Studio 2012 is definitely supported by VsVim.  Do you have a non-express version of 2012 installed?  The express SKU's don't support any extensions which includes VsVim

Indeed, thank you. I have the Express version... I will try this plugin with a trial version :)

Hi,

I am in VS2012, vsvim 1.3.1.3.
Without vsvim installed, the highlight current line is no problem.

After installd vsvim, by default the highlight current line is switched off.

I tried to put the line 

set cursorline

in _vsvimrc. But it doesn't work.

Type: :set cursorline? Got: nocusorline
Type: :set vimrc Got: vimrc="C:\Users\nli\_vsvimrc"
Type: :set cursorline, The highlight current line is working.

Is it a bug?

Thanks for reporting.

Yes this is a known issue with the current release of VsVim.  It is fixed for the upcoming version of VsVim though which will be released in the beginning of January.  

Thanks for quick response.

Hi,

I just upgraded to vsvim to 1.3.2.0. This issue seems be no change in this version. Is it supposed by fixed in this verstion?

Thanks,
Nan

Sorry, unfortunately this was not fixed.  There was a general issue with VimRc files that I fixed which I thought would take care of this.  

Upon further investigation this is a separate issue.  I looked into the problem this morning and I know what the fix is.  I'll be making the fix this evening and will likely publish a beta release that includes it at that time.  I will post a link here when that happens.  

I see.

Great thanks.

Here is the link to the patched drop.  

https://www.dropbox.com/s/ln2cg7gtzc0zmbx/VsVim-CursorLine.vsix

I tested this out locally on my machine and the cursorline setting from my vimrc file is being loaded in Visual Studio.  

To install this you'll need to first uninstall VsVim from your Visual Studio instance.  Then just download that file and double click on it. 

Yes, it works for me.

Look forwards to seeing this fix into official release.

Thanks a lot.

Glad to hear it's working for you! 

Does :tabe not work?

I'm new to vim in general, and it's one of the things I was hoping would be in VsVim since I've come to dislike using my mouse to open/switch tabs.  :tabn, :tabp and gt/gT work like a charm.

Thanks for reporting the issue.

Right now `:tabe` isn't implemented but it's on the list for an upcoming version.  Hopefully by 1.3.2.2