From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 57102@debbugs.gnu.org
Subject: bug#57102: 29.0.50; Peculiar file-name-split edge case
Date: Fri, 12 Aug 2022 17:59:49 +0200 [thread overview]
Message-ID: <87lertlafe.fsf@gnus.org> (raw)
In-Reply-To: <87bkspa225.fsf@posteo.net> (Philip Kaludercic's message of "Fri, 12 Aug 2022 15:56:02 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> How sensible is this in the first place? Shouldn't it rather be
> something like
>
> (file-equal-p (apply #'file-name-concat (file-name-split filename)) filename)
>
> [ which is currently likewise not given ]
>
> Or to put it differently, who does the preceding empty string benefit if
> we ignore the condition mentioned in the docstring? Are there any
> real-world use-cases?
You need to be able to tell (file-name-split "a/b") => ("a" "b") and
(file-name-split "/a/b") => ("" "a" "b") apart.
next prev parent reply other threads:[~2022-08-12 15:59 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lertlafe.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57102@debbugs.gnu.org \
--cc=philipk@posteo.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).