Re: cygpath "$@" in a script: bug?

2003-03-10 Thread Randall R Schulz
Ralf, Yes. Well, no. Cygpath isn't "chok[ing]." It's operating correctly. It accepts one input name per line when used in filter mode. You can use tr or sed to insert newlines where appropriate, but it's not feasible to have cygpath interpret spaces as separators between input names. Since spa

RE: cygpath "$@" in a script: bug?

2003-03-10 Thread Igor Pechtchanski
> > From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] > > Sent: Montag, 10. Marz 2003 16:05 > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: Re: cygpath "$@" in a script: bug? > [...] > > > > Yes, it needs the newlines (LF is enoug

Re: cygpath "$@" in a script: bug?

2003-03-10 Thread Tino Lange
Then you will call cygpath x-times, which is quite inefficient for large globbing with wildcards. Better do something like *** snip *** #! /bin/sh for file in "$@"; do memfile="${memfile:-""}$file\n" done $(echo -e "$memfile" | cygpath -w -f -) *** snip *** which results in just one call vi

Re: cygpath "$@" in a script: bug?

2003-03-10 Thread Igor Pechtchanski
On Mon, 10 Mar 2003, Ralf Hauser wrote: > in http://sources.redhat.com/ml/cygwin/2003-01/msg01707.html I thought to > see how I should do this. > The example works fine. But if I create a script that does > the same > > echo "$@" | cygpath -w -f - > > and call it with > > testscript `/bin/ls /bin/

cygpath "$@" in a script: bug?

2003-03-10 Thread Ralf Hauser
in http://sources.redhat.com/ml/cygwin/2003-01/msg01707.html I thought to see how I should do this. The example works fine. But if I create a script that does the same echo "$@" | cygpath -w -f - and call it with testscript `/bin/ls /bin/ch*` I get C:\cygwin\bin\checkgid.exe \bin\chgrp.exe \bi