unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36490@debbugs.gnu.org, erik_hahn@gmx.de
Subject: bug#36490: 26.1; directory-files-recursively breaks when it encounters a directory named "~"
Date: Wed, 10 Jul 2019 13:55:33 +0200	[thread overview]
Message-ID: <m3h87u14ui.fsf@gnus.org> (raw)
In-Reply-To: <83sgrf3yx5.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 09 Jul 2019 20:23:02 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> "~/" isn't something you'll ever get from functions like
>> directory-files
>
> That's sheer luck, because:
>
>   (file-name-as-directory "~")
>     => "~/"
>
> So just running "~" through an innocent API gives you a "magic"
> directory name (if you consider "~" not "magic" by itself).  How is
> this different from the "odd" use case where one must quote "~" to
> avoid its interpretation as the home directory?  Who can guarantee
> that some day directory-files-recursively will not want to do
> something like the above?  If it does, we will be right back at the
> same problem.

Well...  That kinda sounds odd to me.

"~/" is not, and never will be, a valid file name in any OS that Emacs
is going to support from now on.  So having that have a special meaning
in `expand-file-name' is not surprising.  Having "~" do something
special is surprising.

But changing that is probably not going to happen, so how about just
clarifying the documentation in that function to say what "~" means
explicitly instead of the caller having to guess?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2019-07-10 11:55 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
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 [this message]
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=m3h87u14ui.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=36490@debbugs.gnu.org \
    --cc=eliz@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).