From: Andrey Repin <anrdaemon@yandex.ru>
To: Roger Qiu <roger.qiu@polycademy.com>, cygwin@cygwin.com
Subject: Re: cygpath -w converts relative paths to absolute windows paths
Date: Tue, 07 Feb 2017 15:35:00 -0000 [thread overview]
Message-ID: <357614277.20170207183005@yandex.ru> (raw)
In-Reply-To: <10eb657d-a00b-1609-a9b9-6373092c1ac1@polyhack.io>
Greetings, Roger Qiu!
> Hi,
> I've found that `cygpath --windows '../` will give back an absolute
> windows path.
> I thought this would only happen if you provide the `--absolute` flag,
> or when the path is a special cygwin path.
".." is a special path, that can't be safely converted.
In all cases, using absolute path is preferred for many reasons.
> But this occurs just for normal directories.
> I have come across a situation where I need to convert ntfs symlinks to
> unix symlinks and back. Sometimes these symlinks have relative paths
> them. Now by using cygpath --windows, I get back absolute paths, which
> means the integrity of the symlink isn't preserved.
> Can `cygpath --windows '../directory'` give back `..\directory` for
> paths aren't special cygwin paths? These relative backslashes are
> supported in Windows right now.
AFAIK, Windows do not support relative junction points.
--
With best regards,
Andrey Repin
Tuesday, February 7, 2017 18:27:52
Sorry for my terrible english...
--
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
next prev parent reply other threads:[~2017-02-07 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 3:36 Roger Qiu
2017-02-07 15:35 ` Andrey Repin [this message]
2017-02-07 23:13 ` cyg Simple
2017-02-07 23:34 ` Thomas Wolff
2017-02-08 1:00 ` Brian Inglis
2017-02-08 11:06 ` Andrey Repin
2017-02-08 22:42 ` Thomas Wolff
2017-02-11 21:27 ` cyg Simple
2017-02-09 1:17 ` Roger Qiu
2017-02-12 11:23 ` Corinna Vinschen
2017-02-12 17:39 ` Thomas Wolff
2017-02-13 15:16 ` Corinna Vinschen
2017-02-13 19:34 ` Thomas Wolff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=357614277.20170207183005@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=roger.qiu@polycademy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).