This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: cygpath usage (was: RE: Posible bug in cygpath Windows -> Unix conversion)
- To: Andrej Borsenkow <Andrej dot Borsenkow at mow dot siemens dot ru>
- Subject: Re: cygpath usage (was: RE: Posible bug in cygpath Windows -> Unix conversion)
- From: Bob McGowan <rmcgowan at veritas dot com>
- Date: Wed, 10 Apr 2024 09:37:55 -0700
- CC: Cygwin mailing list <Cygwin at Sourceware dot Cygnus dot Com>
- Organization: VERITAS Software
- References: <000501c03282$23152720$21c9ca95@mow.siemens.ru>
Nope, you are right. I was just pointing out that, looking at the
results of:
cygpath -a -u a:abc
and
cygpath -u a:abc
it looks like the command is treating the argument as absolute also, in
this case.
There was another message on this thread from Chris Faylor saying he had
found the cause of the problem and fixed it.
Andrej Borsenkow wrote:
>
> >
> > It looks like the conversion assumes a "drive_letter:slash" and so is
> > cutting the first 3 characters, producing the output you see. This is
> > probably the result of using the -a option, forcing cygpath to assume
> > the source string is an absolute path when in fact it is not.
> >
>
> I believe, the option -a means, that the *result* should be absolute path.
> Look here:
>
> mw1g017@MW1G17C% cygpath -a -u foo
> /cygdrive/c/win32app/bin/foo
> mw1g017@MW1G17C% cygpath -a -w foo
> c:\win32app\bin\foo
>
> At least, I always understood it this way. Correct me if I'm wrong.
>
> -andrej
--
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan@veritas.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com