From: Eli Zaretskii <eliz@gnu.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: schwab@linux-m68k.org, 43375@debbugs.gnu.org
Subject: bug#43375: 26.1: file-directory-p returns t for empty string
Date: Sun, 13 Sep 2020 19:47:35 +0300 [thread overview]
Message-ID: <83lfhdbp3s.fsf@gnu.org> (raw)
In-Reply-To: <20200913162900.rhsfskhrdqi5odao@E15-2016.optimum.net> (message from Boruch Baum on Sun, 13 Sep 2020 12:29:00 -0400)
> Date: Sun, 13 Sep 2020 12:29:00 -0400
> From: Boruch Baum <boruch_baum@gmx.com>
> Cc: schwab@linux-m68k.org, 43375@debbugs.gnu.org
>
> > I'm okay with making the doc string more clear, but let's please think
> > about a more useful amendment. A doc string should help the user
> > understand what will/did happen, it shouldn't present puzzles.
>
> How about:
>
> Return t if evaluating `expand-file-name' on FILENAME names an existing
> directory.
How does that help the reader predict what will happen in each and
every case without actually trying?
Anyway, I think this is a moot point, since Lars already fixed the doc
string to mention this special case, and the current text is clear
enough to my palate.
next prev parent reply other threads:[~2020-09-13 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 12:47 bug#43375: 26.1: file-directory-p returns t for empty string Boruch Baum
2020-09-13 13:06 ` Andreas Schwab
2020-09-13 13:34 ` Lars Ingebrigtsen
2020-09-13 14:40 ` Boruch Baum
2020-09-13 14:39 ` Boruch Baum
2020-09-13 15:01 ` Eli Zaretskii
2020-09-13 16:29 ` Boruch Baum
2020-09-13 16:47 ` Eli Zaretskii [this message]
2020-09-13 15:56 ` Andreas Schwab
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=83lfhdbp3s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43375@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
--cc=schwab@linux-m68k.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.