From: Lars Ingebrigtsen <larsi@gnus.org>
To: Erik Hahn <erik_hahn@gmx.de>
Cc: 36490@debbugs.gnu.org
Subject: bug#36490: 26.1; directory-files-recursively breaks when it encounters a directory named "~"
Date: Mon, 08 Jul 2019 23:56:40 +0200 [thread overview]
Message-ID: <m38st8197r.fsf@gnus.org> (raw)
In-Reply-To: <bbc36f76-4b29-108c-218f-5a95efb512c8@gmx.de> (Erik Hahn's message of "Mon, 8 Jul 2019 23:30:38 +0200")
Erik Hahn <erik_hahn@gmx.de> writes:
> It is related in that it also chokes on files named "~":
>
> (substitute-in-file-name "/tmp/~") => "~"
>
> Its doc string is also wrong. It says
>
>> If ‘/~’ appears, all of FILENAME through that ‘/’ is discarded.
>
> but
>
> (substitute-in-file-name "/tmp/~foo") => "/tmp/~foo"
Yup, it's only if the user exists:
(substitute-in-file-name "/tmp/~larsi")
=> "~larsi"
Same as with expand-file-name:
(expand-file-name "~larsi" "/tmp/")
=> "/home/larsi"
(expand-file-name "~foo" "/tmp/")
=> "/tmp/~foo"
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-08 21:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 18:07 bug#36490: 26.1; directory-files-recursively breaks when it encounters a directory named "~" Erik Hahn
2019-07-08 20:59 ` Lars Ingebrigtsen
2019-07-08 21:08 ` Lars Ingebrigtsen
2019-07-08 21:30 ` Erik Hahn
2019-07-08 21:56 ` Lars Ingebrigtsen [this message]
2019-07-09 15:39 ` Eli Zaretskii
2019-07-09 15:35 ` Eli Zaretskii
2019-07-09 15:50 ` Lars Ingebrigtsen
2019-07-09 16:12 ` Eli Zaretskii
2019-07-09 16:27 ` Lars Ingebrigtsen
2019-07-09 16:44 ` Eli Zaretskii
2019-07-09 16:50 ` Lars Ingebrigtsen
2019-07-09 16:52 ` Eli Zaretskii
2019-07-09 17:00 ` Lars Ingebrigtsen
2019-07-09 17:23 ` Eli Zaretskii
2019-07-09 18:16 ` Michael Albinus
2019-07-10 11:55 ` Lars Ingebrigtsen
2019-07-10 14:56 ` Eli Zaretskii
2019-07-11 15:05 ` Lars Ingebrigtsen
2019-07-09 18:58 ` Basil L. Contovounesios
2019-07-09 19:19 ` Eli Zaretskii
2019-07-09 16:17 ` Andreas Schwab
2019-07-10 12:04 ` Lars Ingebrigtsen
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=m38st8197r.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=36490@debbugs.gnu.org \
--cc=erik_hahn@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.
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).