Why does robocopy confuse input and output files defined with Cygwin/bash and perl?

Why does robocopy confuse input and output files defined with Cygwin/bash and perl?

[siegfried]

I sent this once and it did not appear in the list. Maybe I typed the
list name wrong? 
I apologize if this appears twice.


I think the following code below should work (unfortunately, my email
program wants to wrap the code). The results of the echo
statement look fine! When I cut and paste the results of the echo, the
robocopy command works great!

OK! Now I want to automate it and instead of just displaying the
robocopy command with echo, actually execute it! 
But why won't it execute directly?

For some reason, I get the errors below. Why is robocopy getting
confused on the input and output files?



Thanks
siegfried





src=$(perl -e '$u = $ENV{"USERNAME"};$s = $_ = $ARGV[0]; $_ =
lcfirst;s@[/\\]@\\\\@g; s@\s@\\ @g; s/(.):/$1\\:/; print " $_";
'"$(cygpath -w $PWD)")
dst=$(perl -e '$u = $ENV{"USERNAME"}; $_ = $ARGV[0]; $_ = lcfirst;
s@(/cygdrive/c|c:)[/\\]+Users[/\\]+$u([/\\]+Documents([/\\]+)?)?@f:\\backup\\unison\\@g;s@(c:\\cygwin(64)?)?[\\/]+home[\\/]+$u([\\/]+)?@f:\\backup\\unison\\HOME\\@g;s@[/\\]@\\\\@g;
s@\s@\\ @g; s/(.):/$1\\:/; print " $_"; $p="";foreach (split "[/\\\\]"){
$p = $p.$_."/"; mkdir $p unless -e $p } ' "$(cygpath -w $PWD)")
echo src=$src
echo dst=$dst
echo robocopy /s $src $dst
robocopy $src $dst

--- output from above commands:

src= c\:\\Users\\siegfried\\Documents\\bin
dst= f\:\\backup\\unison\\bin
robocopy /s c\:\\Users\\siegfried\\Documents\\bin
f\:\\backup\\unison\\bin

-------------------------------------------------------------------------------
ROBOCOPY :: Robust File Copy for Windows 

-------------------------------------------------------------------------------

Started : Tuesday, September 29, 2015 7:53:04 PM
Source :
c:\Users\siegfried\Documents\bin\c\:\Users\siegfried\Documents\bin\
Dest : c:\Users\siegfried\Documents\bin\f\:\backup\unison\bin\

Files : *.*

Options : *.* /DCOPY:DA /COPY:DAT /R:1000000 /W:30 

------------------------------------------------------------------------------

2015/09/29 19:53:04 ERROR 123 (0x0000007B) Accessing Source Directory
c:\Users\siegfried\Documents\bin\c\:\Users\siegfried\Documents\bin\
The filename, directory name, or volume label syntax is incorrect.

Compilation exited abnormally with code 16 at Tue Sep 29 19:53:04

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

Re: Why does robocopy confuse input and output files defined with Cygwin/bash and perl?

[Eliot Moss]

Dealing with "odd" characters like \ and such can be a pain, huh?
Perhaps it will help you to know that bash will expand variables
inside double-quoted arguments, i.e., "${src}".  (You can write
"$src" if you want, but over the years I am finding it clearer /
better to use the { } to make clear the name of the variable I
want expanded.)

Also, you may find the cygpath utility helpful, and the $( ) idiom
of bash.  Thus:

robocopy /s "$(cygpath -w /cygdrive/c/Users/siegfriend/Documents/bin)" "$(cygpath -w 
/cygdrive/f/backup/unison/bin)"

I believe this will do what you want.  cygpath can be very helpful
hen you desire to run a Windows program from the cygwin environment.

Regards -- Eliot Moss

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

Re: Why does robocopy confuse input and output files defined with Cygwin/bash and perl?

[Andrey Repin]

Greetings, Eliot Moss!

> Dealing with "odd" characters like \ and such can be a pain, huh?
> Perhaps it will help you to know that bash will expand variables
> inside double-quoted arguments, i.e., "${src}".  (You can write
> "$src" if you want, but over the years I am finding it clearer /
> better to use the { } to make clear the name of the variable I
> want expanded.)

> Also, you may find the cygpath utility helpful, and the $( ) idiom
> of bash.

It isn't "idiom of bash", it is a POSIX construction.

> Thus:

> robocopy /s "$(cygpath -w /cygdrive/c/Users/siegfriend/Documents/bin)" "$(cygpath -w
> /cygdrive/f/backup/unison/bin)"

> I believe this will do what you want.  cygpath can be very helpful
> hen you desire to run a Windows program from the cygwin environment.

I would suggest cygpath -m.


-- 
With best regards,
Andrey Repin
Wednesday, September 30, 2015 22:26:55

Sorry for my terrible english...


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

Re: Why does robocopy confuse input and output files defined with Cygwin/bash and perl?

[cyg Simple]

On 9/30/2015 3:27 PM, Andrey Repin wrote:
> Greetings, Eliot Moss!
> 
>> Dealing with "odd" characters like \ and such can be a pain, huh?
>> Perhaps it will help you to know that bash will expand variables
>> inside double-quoted arguments, i.e., "${src}".  (You can write
>> "$src" if you want, but over the years I am finding it clearer /
>> better to use the { } to make clear the name of the variable I
>> want expanded.)
> 
>> Also, you may find the cygpath utility helpful, and the $( ) idiom
>> of bash.
> 
> It isn't "idiom of bash", it is a POSIX construction.
> 
>> Thus:
> 
>> robocopy /s "$(cygpath -w /cygdrive/c/Users/siegfriend/Documents/bin)" "$(cygpath -w
>> /cygdrive/f/backup/unison/bin)"
> 
>> I believe this will do what you want.  cygpath can be very helpful
>> hen you desire to run a Windows program from the cygwin environment.
> 
> I would suggest cygpath -m.

Not for robocopy, it is likely not to survive / instead of \.  I would
prefix it with "cmd /c" though or perhaps create a bash script called
robocopy to do the path conversion before calling the Windows
robocopy.exe.  That way the command line looks typical.

-- 
cyg Simple

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