On Wednesday, May 14, 2014 9:46:32 AM UTC-5, Stromek Doe wrote:
> On Friday, October 11, 2013 7:59:47 AM UTC+2, star...@gmail.com wrote:
> > So change:
> > if &sh =~ '\<cmd' (fails)
> >
> > To:
> > if &sh =~ "\<cmd" (works)
>
> This worked for me on Windows 7.
That is the WRONG solution, as I pointed out in the exact next message. What this change does, is it BREAKS the test for the cmd shell. Instead of matching "cmd" as a whole word, now it will try matching "<cmd" with a literal < before it. Obviously this will not match your actual shell on Windows.
The ACTUAL PROBLEM is that the code for the cmd.exe shell was broken.
This problem HAS BEEN FIXED in the latest version of the Vim installer by actually fixing the code for cmd.exe. Unfortunately Bram does not update the "official" installers very often.
So, you can either get an installer from an alternate source: http://vim.wikia.com/wiki/Where_to_download_Vim
Or compile yourself and run the installer: http://vim.wikia.com/wiki/Building_Vim#Building_Vim_on_Windows
Or just copy the result of the default installed .vimrc: http://superuser.com/questions/697847/cant-run-vimdiff-7-4-on-windows-7/697914#697914
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Wednesday, May 14, 2014
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment