From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: michael_heerdegen@web.de, 17073@debbugs.gnu.org
Subject: bug#17073: 24.3.50; file-symlink-p doesn't return t as described in the doc
Date: Mon, 24 Mar 2014 05:52:31 +0200 [thread overview]
Message-ID: <83vbv41ce8.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SS45WagvQ+i4-CQoZCUzs4xxzk9ZweBSeSHHcBDe0cq+A@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 24 Mar 2014 01:25:36 +0100
>
> Perhaps it's me, but I don't find the doc for this function (in the
> elisp reference) particularly clear
>
> -- Function: file-symlink-p filename
> If the file FILENAME is a symbolic link, the `file-symlink-p'
> function returns the (non-recursive) link target as a string.
>
> Here it agrees with your interpretation, so at least that is clear.
>
> (Determining the file name that the link points to from the target
> is nontrivial.) First, this function recursively follows symbolic
> links at all levels of parent directories.
>
> IIUC, it's saying (above) that it does not follow symbolic links to
> files recursively. But (below) that it does follow recursively
> symbolic links to directories, until it finds a file (or a symbolic
> link to a file). Is that?
The difference is between the file (a.k.a. "basename") part of the
file name, and the leading directories part. And yes, it is true.
next prev parent reply other threads:[~2014-03-24 3:52 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83vbv41ce8.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 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.