Re: 'run' command quirks

2006-03-31 Thread Alexander Gottwald
On Fri, 2006-03-31 at 09:17 -0500, Igor Peshansky wrote: > > run has no problem with /cygdrive (it's linked with cygwin1.dll, after > all). What confuses it are the spaces in the path. From a quick look at > the run source, it parses the command line twice -- once to skip the > executable name,

Re: 'run' command quirks

2006-03-31 Thread Igor Peshansky
On Thu, 30 Mar 2006, Eric Blake wrote: > According to Jerry D. Hedden on 3/29/2006 8:02 AM: > > I am trying to run the Windows version of gVim from a bash script using > > the 'run' command. > > > > However, the following fails: > > run '/cygdrive/c/program files/vim/vim64/gvim.exe' > > with t

Re: 'run' command quirks

2006-03-30 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jerry D. Hedden on 3/29/2006 8:02 AM: > I am trying to run the Windows version of gVim from a bash script using > the 'run' command. > > However, the following fails: > run '/cygdrive/c/program files/vim/vim64/gvim.exe' > with the fol

'run' command quirks

2006-03-29 Thread Jerry D. Hedden
I am trying to run the Windows version of gVim from a bash script using the 'run' command. Starting gVim directly (i.e., without using 'run') works: '/cygdrive/c/program files/vim/vim64/gvim.exe' Using 'run' works if I 'cd' to the gVim directory first: cd '/cygdrive/c/program files/vim/vi