From: Gregory Heytings <gregory@heytings.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Philip Kaludercic <philipk@posteo.net>,
Lars Ingebrigtsen <larsi@gnus.org>,
57102@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#57102: 29.0.50; Peculiar file-name-split edge case
Date: Mon, 26 Sep 2022 12:27:59 +0000 [thread overview]
Message-ID: <0f4ca4f3318d4005587a@heytings.org> (raw)
In-Reply-To: <DB004E36-033A-470C-AEB7-B75DA09586E3@acm.org>
>> One small step in the right direction would be to make sure that:
>>
>> (equal (file-name-split "/foo")
>> (file-name-split "//foo"))
>
> There's the Posix peculiarity that /abc and //abc are potentially
> distinct, but ///abc should be equivalent to /abc if I understood it
> right.
>
Indeed, POSIX says that "A pathname that begins with two successive
<slash> characters may be interpreted in an implementation-defined manner,
although more than two leading <slash> characters shall be treated as a
single <slash> character."
next prev parent reply other threads:[~2022-09-26 12:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 8:24 bug#57102: 29.0.50; Peculiar file-name-split edge case Philip Kaludercic
2022-08-12 15:35 ` Lars Ingebrigtsen
2022-08-12 15:56 ` Philip Kaludercic
2022-08-12 15:59 ` Lars Ingebrigtsen
2022-08-12 16:29 ` Philip Kaludercic
2022-08-13 11:44 ` Lars Ingebrigtsen
2022-08-13 13:24 ` Philip Kaludercic
2022-08-15 5:54 ` Lars Ingebrigtsen
2022-08-15 11:28 ` Lars Ingebrigtsen
2022-08-15 15:57 ` Philip Kaludercic
2022-08-15 11:35 ` Eli Zaretskii
2022-08-17 10:55 ` Lars Ingebrigtsen
2022-08-13 18:06 ` Augusto Stoffel
2022-08-14 6:24 ` Philip Kaludercic
2022-08-13 17:08 ` Mattias Engdegård
2022-09-25 12:06 ` Stefan Kangas
2022-09-26 10:41 ` Lars Ingebrigtsen
2022-09-26 11:14 ` Stefan Kangas
2022-09-26 11:59 ` Lars Ingebrigtsen
2022-09-26 12:07 ` Mattias Engdegård
2022-09-26 12:27 ` Gregory Heytings [this message]
2022-09-29 3:02 ` Richard Stallman
2022-09-29 6:20 ` Eli Zaretskii
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=0f4ca4f3318d4005587a@heytings.org \
--to=gregory@heytings.org \
--cc=57102@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=philipk@posteo.net \
--cc=stefankangas@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.