From: Stephane Chazelas <stephane@chazelas.org>
To: zsh-workers@zsh.org
Subject: Re: glob qualifier '-' doesn't work correctly on dangling symlinks
Date: Sun, 12 Apr 2020 18:34:48 +0100 [thread overview]
Message-ID: <20200412173448.rl3wttigdx5t5wcn@chazelas.org> (raw)
In-Reply-To: <20200412142544.GA1783815@zira.vinc17.org>
2020-04-12 16:25:44 +0200, Vincent Lefevre:
[...]
> > by the link, and not the link itself. If the
> > ^^^^^^
> > referenced file does not exist, the file information
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > and type shall be for the link itself.
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> At least, that's explicit, unambiguous documentation.
[...]
Well, as seen in the varying interpretations made by the various
implementations, it is not that clear. How do you determine
whether a file exists or not? What does "exist" mean?
If ENOENT or ENOTDIR is returned upon stat(), you can tell
there's no file at that path, but it's not so clear with ELOOP,
EACCES, EOVERFLOW, ENOMEM for instance, where we can't tell for
sure the file doesn't "exist". If didn't exist for the caller at
the time in that it can't access it, but it may exist in the
"absolute" or for a caller with different credentials or in a
different namespace (could also apply for ENOENT/ENOTDIR in that
case)..
That was discussed on the austin-group mailing list not so long
ago wrt glob(3)
https://www.mail-archive.com/austin-group-l@opengroup.org/msg04496.html
https://www.austingroupbugs.net/view.php?id=1275
--
Stephane
next prev parent reply other threads:[~2020-04-12 17:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 15:15 Vincent Lefevre
2020-04-11 17:34 ` Stephane Chazelas
2020-04-11 19:17 ` Vincent Lefevre
2020-04-11 20:37 ` Stephane Chazelas
2020-04-11 23:48 ` Vincent Lefevre
2020-04-12 1:21 ` Daniel Shahaf
2020-04-12 2:17 ` Vincent Lefevre
2020-04-12 7:09 ` Stephane Chazelas
2020-04-12 14:25 ` Vincent Lefevre
2020-04-12 17:34 ` Stephane Chazelas [this message]
2020-04-12 23:38 ` Vincent Lefevre
2020-04-13 14:22 ` Stephane Chazelas
2020-04-13 15:00 ` Bart Schaefer
2020-04-13 21:41 ` Vincent Lefevre
2020-04-14 6:18 ` Stephane Chazelas
2020-04-14 12:02 ` Daniel Shahaf
2020-04-14 12:38 ` Stephane Chazelas
2020-04-15 0:44 ` Daniel Shahaf
2020-04-15 9:17 ` Vincent Lefevre
2020-04-14 17:59 ` Vincent Lefevre
2020-04-12 12:48 ` Peter Stephenson
2020-04-12 14:31 ` Vincent Lefevre
2020-04-12 15:49 ` Peter Stephenson
2020-04-12 23:07 ` Vincent Lefevre
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=20200412173448.rl3wttigdx5t5wcn@chazelas.org \
--to=stephane@chazelas.org \
--cc=zsh-workers@zsh.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 public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).