From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: lekktu@gmail.com, 17073@debbugs.gnu.org
Subject: bug#17073: 24.3.50; file-symlink-p doesn't return t as described in the doc
Date: Tue, 25 Mar 2014 21:02:20 +0200 [thread overview]
Message-ID: <83mwgeyudf.fsf@gnu.org> (raw)
In-Reply-To: <87d2ha15vs.fsf@web.de>
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Juanma Barranquero <lekktu@gmail.com>, 17073@debbugs.gnu.org
> Date: Tue, 25 Mar 2014 19:37:43 +0100
>
> If the leading directories of @var{filename} include symbolic links,
> this function recursively follows them.
>
> Is this obvious?
Hard to say. I think it's pretty obvious to those who are used to
semantics of symlinks (I actually find strange and even confusing the
fact that the manual insists on telling which functions follow links
and in which parts of the filename). For those who are not used to
symlinks, I'm pretty sure even the above sentence does not say enough.
> If not - doesn't it also belong in the docstring?
Well, we don't normally say about each file-related function whether
it does or doesn't follow symlinks. So why this one?
next prev parent reply other threads:[~2014-03-25 19:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 19:33 bug#17073: 24.3.50; file-symlink-p doesn't return t as described in the doc Michael Heerdegen
2014-03-23 23:34 ` Glenn Morris
2014-03-23 23:39 ` Glenn Morris
2014-03-24 0:25 ` Juanma Barranquero
2014-03-24 3:52 ` Eli Zaretskii
2014-03-24 4:00 ` Juanma Barranquero
2014-03-24 4:02 ` Juanma Barranquero
2014-03-24 16:49 ` Eli Zaretskii
2014-03-24 17:01 ` Juanma Barranquero
2014-03-25 16:10 ` Eli Zaretskii
2014-03-25 16:29 ` Juanma Barranquero
2014-03-25 18:03 ` Eli Zaretskii
2014-03-25 18:04 ` Juanma Barranquero
2014-03-25 18:37 ` Michael Heerdegen
2014-03-25 19:02 ` Eli Zaretskii [this message]
2014-03-25 19:21 ` Michael Heerdegen
2014-03-26 0:41 ` Stefan Monnier
2014-03-26 3:53 ` 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
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=83mwgeyudf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17073@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=michael_heerdegen@web.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).