From: Andrey Repin <anrdaemon@yandex.ru>
To: "Sven Eden" <sven.eden@gmx.de>, cygwin@cygwin.com
Subject: Re: Problematic interpretion of paths starting with double slashes
Date: Wed, 13 Jun 2018 13:49:00 -0000 [thread overview]
Message-ID: <183057486.20180613155036@yandex.ru> (raw)
In-Reply-To: <trinity-709441a4-b53d-4bbd-96fb-91ad85816938-1528878894364@3c-app-gmx-bs06>
Greetings, Sven Eden!
>> Gesendet: Dienstag, 12. Juni 2018 um 18:28 Uhr
>> Von: "Brian Inglis" <Brian.Inglis@SystematicSw.ab.ca>
>> On 2018-06-12 07:14, Sven Eden wrote:
>> >> Gesendet: Dienstag, 12. Juni 2018 um 13:52 Uhr
>> >> Von: "Eric Blake" <eblake@redhat.com>
>> >> Then fix your script to provide 3 slashes instead of 2. Only 2 slashes
>> >> has the magic UNC behavior.
>> > It is not my script. *my* scripts are portable by all means.
>> >> That is, if you have a script that is concatenating:
>> >> ${prefix}/${dir}
>> >> where ${prefix} might be empty, you can always rewrite it to be:
>> >> ${prefix}///${dir}
>> > The script was "fixed" from ${prefix}/${dir} a while ago. Before that the
>> > outcome was "///". Which is very bad style. Good style is to guarantee, that
>> > not more than one slash is issued.
>>
>> Which is equivalent to //localhost/ on Cygwin and elsewhere - / on Linux - this
>> is semantics not "style".
> I talked about replacing something wrong with something
> worse. That's style, not semantics. But I get what you are
> meaning. ;-)
If it is documented, it is not wrong.
> However, from my two questions, one was answered, and I can
> figure out the other just fine by myself.
> Q: Can the handling of // be extended to check for / if the
> first fails?
> A: Yes
Can? Yes. Purely technically. But for consistency it will not be.
Ambiguous paths are a big no-no.
--
With best regards,
Andrey Repin
Wednesday, June 13, 2018 15:48:59
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:[~2018-06-13 13:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 11:45 Sven Eden
2018-06-12 11:52 ` Adam Dinwoodie
2018-06-12 16:28 ` Eric Blake
2018-06-12 17:12 ` Aw: " Sven Eden
2018-06-12 17:57 ` Brian Inglis
2018-06-13 10:14 ` Aw: " Sven Eden
2018-06-13 13:49 ` Andrey Repin [this message]
2018-06-15 2:41 ` Brian Inglis
2018-06-12 20:01 ` Aw: " Eric Blake
2018-06-13 13:05 ` Sven Eden
2018-06-12 20:32 ` Lee
2018-06-13 13:05 ` Aw: " Sven Eden
2018-06-12 23:31 ` Aw: " Achim Gratz
2018-06-13 9:57 ` Corinna Vinschen
2018-06-13 13:29 ` Sven Eden
2018-06-13 19:32 ` Achim Gratz
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=183057486.20180613155036@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=sven.eden@gmx.de \
/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).