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: Re: need help with bash -c <command> with cygpath


On 11 January 2008 15:51, Phil Betts wrote:

> If you absolutely MUST have backslashes, from cmd.exe, you need to
> double each backslash:
> 
> H:\>C:\cygwin\bin\bash -v -c '\\\\UNC_PATH\\Dir'
> 

  That doesn't work for me.  Adding the '-x' option to bash is very handy for
debugging these sorts of problems, it shows you what bash thinks it's actually
seeing:-


C:\Documents and Settings\dk>C:\cygwin\bin\bash -v -x -c '\\\\UNC_PATH\\Dir'
\\UNC_PATH\Dir
+ '\UNC_PATHDir'
/usr/bin/bash: \UNC_PATHDir: command not found


  I believe what is needed is 1) outer double-quotes, for cmd's benefit, 2)
inner single-quotes, for bash's benefit, 3) double up the slashes /as well/,
because there's one more level of quoting being stripped than I can account
for, but anyway it works for me:

C:\Documents and Settings\dk>C:\cygwin\bin\bash -v -x -c "'\\\\UNC_PATH\\Dir'"
'\\UNC_PATH\Dir'
+ '\\UNC_PATH\Dir'
/usr/bin/bash: \\UNC_PATH\Dir: command not found

C:\Documents and Settings\dk>


  If I wasn't trying to execute a directory but list it instead, I'd say

C:\cygwin\bin\bash -v -x -c "ls -la '\\\\UNC_PATH\\Dir'"

(just using this example to illustrate how the outer quotes protect the bash
commandline from cmd, and the inner quotes are part of the bash commandline).

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


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