From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
"Philip Kaludercic" <philipk@posteo.net>,
57102@debbugs.gnu.org
Subject: bug#57102: 29.0.50; Peculiar file-name-split edge case
Date: Mon, 26 Sep 2022 13:59:22 +0200 [thread overview]
Message-ID: <87o7v273dx.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmnh7V2OVJxOWYX5r8U5xrZ+8F=-SWNJGzTCmjpEVph=hw@mail.gmail.com> (Stefan Kangas's message of "Mon, 26 Sep 2022 07:14:56 -0400")
Stefan Kangas <stefankangas@gmail.com> writes:
> But, thinking more about this, maybe we would want a new function.
> Because this is not fun:
>
> (apply #'file-name-concat (file-name-split "/foo/bar"))
> => "foo/bar"
Uhm... is that a bug, though?
> I'd like it better if it worked like this:
>
> (file-name-join (file-name-split "/foo/bar"))
> => "/foo/bar"
>
> And then there are the issues Mattias has pointed out. One small step
> in the right direction would be to make sure that:
>
> (equal (file-name-split "/foo")
> (file-name-split "//foo"))
That seems like a bug. :-/
next prev parent reply other threads:[~2022-09-26 11: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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7v273dx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57102@debbugs.gnu.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.