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 -a -C ANSI -w /bin:/usr/bin > C:\cygwin\bin?\usr\bin > > Urk! I would have hoped it wouldn't try to convert this, or at the very > least not the last part, but I don't know if it's a bug, "by design", or > what. > > Basically what I am trying to work out is how trustworthy cygpath is > when it receives input that isn't actually a path (for example when it > receives output from a program, some of which might be paths and some of > which might not be). -- Gary Non-kook (allegedly) -- 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
