Re: Win32 COMSPEC args don't reconfig on COMSPEC resest
- Linda W wrote:
> I changed my COMSPEC on win32 to C:\bin\bash.exe.see
> In vi, when I use the "!" to execute a command on Windows,
> like "ls", it tried to execute it with:
> C:\bin\bash /c ls
> where ^^--- is an argument to the DOS/Windows Shell, but doesn't
> work for for bash.
> Is there some other option to tell Vim not to use the DOS/Windows
> Shell options to non-DOS/Win shells? :-)
> I searched the VIM help: the section on COMSPEC didn't say
> anything relevant, and searching for "/C" ("\/C", "\ \C") didn't turn
> up anything productive.
- A.J.Mechelynck wrote:
> Linda W wrote:---
>> Is there some other option to tell Vim not to use the DOS/Windows
>> Shell options to non-DOS/Win shells? :-)
>> I searched ...
> :help 'shell'
> :help 'shellcmdflag'
> :help 'shellpipe'
> :help 'shellquote'
> :help 'shellredir'
> :help 'shellslash'
> :help 'shelltemp'
> :help 'shellxquote'
> :help dos-shell
> :help option-backslash
- Linda W wrote:
> I changed my COMSPEC on win32 to C:\bin\bash.exe.(snip)
If I use Windows, I tend to use cygwin. I don't suppose you're using
cygwin, as I don't think
you'd need to mess with COMSPEC for it. Anyway, I see Anthony M has
given you some good
clues. The following code snippet is what I use with cygwin's bash;
perhaps it'll give you a start.
To get help on these options, as an example: while in vim, :help 'shq' .
- On 11/3/06, Charles E Campbell Jr <drchip@...> wrote:
> Linda W wrote:FYI. In Windows there are a lot of gotchas when there are special
> > I changed my COMSPEC on win32 to C:\bin\bash.exe.
> If I use Windows, I tend to use cygwin. I don't suppose you're using
> cygwin, as I don't think
> you'd need to mess with COMSPEC for it. Anyway, I see Anthony M has
> given you some good
> clues. The following code snippet is what I use with cygwin's bash;
> perhaps it'll give you a start.
> set shell=bash
> set shq=
> set sxq=\"
> set ssl
> set shcf=-c
> set sp=>&
symbols on the command line, esp. if the shell is not cmd.exe. When
the shell is (ba)sh, try some commands like
:echo system('echo "hel&lo"')
and you know the pain.
Cmd has problems too. With (ba)sh, it is even more painful, since
there is no way to *escape*.
Not a problem of sh itself, since it works perfectly under Cygwin or
Linux. Calling sh in a Windows program is.