From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57102@debbugs.gnu.org
Subject: bug#57102: 29.0.50; Peculiar file-name-split edge case
Date: Sat, 13 Aug 2022 13:24:30 +0000 [thread overview]
Message-ID: <877d3cl1ip.fsf@posteo.net> (raw)
In-Reply-To: <87y1vsjrkx.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 13 Aug 2022 13:44:30 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Could one instead prefix the list with a symbol (either `absolute' or
>> `relative') to distinguish the two cases. Or do you think that would
>> just make it more complicated.
>
> I think that just makes it way more complicated to use.
Grepping through emacs.git to see where file-name-split is used, it
seems that all it would change in most cases you'd just require an
additional (cdr ...). At the same time, there is already an instance in
gnus-search.el that deals with the issue I brought up with the empty
strings.
As another alternative, how about file-name-split takes an optional
argument, and only does what I suggested in that case? From how I see
file-name-split being used up until now (which doesn't have to mean a
lot), that could be a good compromise.
next prev parent reply other threads:[~2022-08-13 13:24 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d3cl1ip.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=57102@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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.