RE: cygpath

["Gluszczak, Glenn" <Glenn.Gluszczak@dell.com>]

Thanks for the explanation.  Just odd how cmd.exe only sometimes misbehaves.

%%%cygpath -w /usr/a/b/*
C:\cygwin\usr\a\b\

%%%cygpath -w /a/b/*
C:\cygwin\a\b\

%%%cygpath -w /a/b/c/*
C:\cygwin\a\b\c\\x15


-----Original Message-----
From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf Of Michael Enright
Sent: Friday, February 10, 2017 3:43 PM
To: cygwin@cygwin.com
Subject: Re: cygpath

On Fri, Feb 10, 2017 at 12:31 PM, Gluszczak, Glenn wrote:
> Sorry, I forgot the user I log in as is switching to cmd.exe.
>
> This doesn't happen in sh or tcsh, so it is probably a non-issue.
>

My results are from running a "normal" bash-under-mintty setup.

If I go to a cmd.exe window and start bash,

Z:\>cygpath -w "/usr/bin/*"
C:\cygwin\bin\?

Z:\>

This is consistent with the explanation that an asterisk ends up having a private-use character substituted in for it.

--
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


--
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