From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygpath -u converts quoted UNC paths to local
Date: Wed, 03 Apr 2019 17:11:00 -0000 [thread overview]
Message-ID: <875zrvm2sw.fsf@Rainer.invalid> (raw)
In-Reply-To: <209675900.20190403192000@yandex.ru> (Andrey Repin's message of "Wed, 3 Apr 2019 19:20:00 +0300")
Andrey Repin writes:
> This can be considered "working by design", but it really imposes some serious
> restrictions on interoperability with Cygwin, that I think can be avoided.
But cygpath never sees the quotes, so whatever is done to the path that
it gets is actually the work of your shell. In other words, you need to
shell-quote the backslashes as appropriate for your shell.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html
--
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:[~2019-04-03 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 16:20 Andrey Repin
2019-04-03 16:31 ` Corinna Vinschen
2019-04-04 7:50 ` Andrey Repin
2019-04-03 17:11 ` Achim Gratz [this message]
2019-04-03 17:42 ` EXT: " Garber, Dave (BHGE, Non-GE)
2019-04-03 17:49 ` Chris Wagner
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=875zrvm2sw.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.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).