This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: window command in bash

Igor Peshansky wrote:
> On Tue, 18 Jul 2006, Buchbinder, Barry (NIH/NIAID) [E] wrote:
>> McGraw, Robert P. wrote:
>>> I have a window command that I want to execute in a bash script.
>>> In my .bat file the command is
>>> 	AgBackup.exe /notext c:\Alligate\agbackupfiles
>>> I tried to execute this command in a bash window and the command
>>> works but is does not seem to recognize the parameters. The
>>> "c:\alligate...." is the path where a backup is written. In the bash
>>> script the backup file is written in the default location. [snip]
>>> In a shell script what is the proper way to pass parameters to a
>>> window program?
>> A Windows program will think that /cygdrive/c/Alligate/agbackupfiles
>> are options, not a path. 
>> Did you quote the path or escape the backslashes to protect the
>> backslashes from the shell interpreting them as escape characters?
>> 	E.g., AgBackup.exe /notext 'c:\Alligate\agbackupfiles'
>> or
>> 	AgBackup.exe /notext "c:\Alligate\agbackupfiles"
> A minor correction: you still need to escape the backslashes when
> using double quotes, so the right way is 
> 	AgBackup.exe /notext "c:\\Alligate\\agbackupfiles"

Here's what bash does:

/c> echo  "c:\Alligate\agbackupfiles"

Maybe if one has a variable following the backslash:

/c> echo "xyz\$USER"
/c> echo "xyz\\$USER"

>> or
>> 	AgBackup.exe /notext c:\\Alligate\\agbackupfiles
>> You should read
>> <>
>> in the Cygwin User's Guide <>, and
>> especially
>> <>. 
> HTH,
> 	Igor

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]