Re: cygpath behaviour when input is not a path

2010-06-02 Thread Gary .
On 6/2/10, Dave Korn wrote: > On 01/06/2010 09:19, Gary . wrote: Since the tool output is mixed paths and text, I'd hoped cygpath made "intelligent" guesses about what was and was not likely to be a path. ... >> Okay. So I'm SOL with tool output like >> "Parse error: syntax error, un

Re: cygpath behaviour when input is not a path

2010-06-02 Thread Dave Korn
On 01/06/2010 09:19, Gary . wrote: > On 5/31/10, Dave Korn wrote: >> On 30/05/2010 08:51, Gary wrote: >>> Since the tool >>> output is mixed paths and text, I'd hoped cygpath made "intelligent" >>> guesses about what was and was not likely to be a path. >>> >> Well, that is basically what it does

Re: cygpath behaviour when input is not a path

2010-06-01 Thread Gary .
On 5/31/10, Dave Korn wrote: > On 30/05/2010 08:51, Gary wrote: >> Since the tool >> output is mixed paths and text, I'd hoped cygpath made "intelligent" >> guesses about what was and was not likely to be a path. >> > > Well, that is basically what it does; but, being a POSIX tool, the > conseque

Re: cygpath behaviour when input is not a path

2010-05-30 Thread Dave Korn
On 30/05/2010 08:51, Gary wrote: > Since the tool > output is mixed paths and text, I'd hoped cygpath made "intelligent" > guesses about what was and was not likely to be a path. > Well, that is basically what it does; but, being a POSIX tool, the consequence is that it assumes that a colon is

Re: cygpath behaviour when input is not a path

2010-05-30 Thread Gary
Andy Koppe wrote: > On 29 May 2010 16:20, Gary wrote: > Have you got any particular reason for overriding the > locale charset with the -C option? Not particularly. I was just reusing the example from http://www.cygwin.com/cygwin-ug-net/using-utils.html I don't think what I want to do is going to

Re: cygpath behaviour when input is not a path

2010-05-29 Thread Andy Koppe
On 29 May 2010 16:20, Gary wrote: > I wrote: >> How should cygcheck > > cygpath, not cygcheck > > /me smacks head > >> behave when given a "PATH list" (e.g., >> '/bin:/usr/bin'), *without* the -p option? >> >> For example: >> $ cygpath -a -p -C ANSI -w /bin:/usr/bin >> C:\cygwin\bin;C:\cygwin\bin >

Re: cygpath behaviour when input is not a path

2010-05-29 Thread Gary
I wrote: > How should cygcheck cygpath, not cygcheck /me smacks head > behave when given a "PATH list" (e.g., > '/bin:/usr/bin'), *without* the -p option? > > For example: > $ cygpath -a -p -C ANSI -w /bin:/usr/bin > C:\cygwin\bin;C:\cygwin\bin > > = okay. What I expect from RTFMP. > > $ cygpath