From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-users@zsh.org
Subject: Unreadable directories aren't included in glob expansion
Date: Thu, 9 Jan 2020 15:41:45 +0000 [thread overview]
Message-ID: <20200109154145.rqksfenozx6745rn@tarpaulin.shahaf.local2> (raw)
Consider:
% mkdir foo
% mkdir -m 000 bar
% echo */
foo/
% echo *(/)
bar foo
%
Shouldn't the expansion of «*/» include «bar/»?
The shell knows, in that situation, that ./bar is a directory; «test -d bar»
and «zstat -or bar» both confirm this.
dash/bash/ksh all include «bar/» in that expansion.
strace shows a probable cause:
.
access("buster/.", F_OK) = -1 EACCES (Permission denied)
I've discussed this on IRC with Eric, but I'd rather let him explain his view
in his own words.
Cheers,
Daniel
P.S. Test case:
diff --git a/Test/D02glob.ztst b/Test/D02glob.ztst
index 5638e1255..1c1663a48 100644
--- a/Test/D02glob.ztst
+++ b/Test/D02glob.ztst
@@ -728,3 +728,10 @@
>does/not/exist
>not/exist
>exist
+
+ mkdir -m 000 glob.tmp/secret1
+ (setopt nullglob
+ echo glob.tmp/*/ glob.tmp/*(/)
+ )
+-f:unreadable directories can be globbed
+>glob.tmp/secret1/ glob.tmp/secret1
next reply other threads:[~2020-01-09 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200109154313eucas1p13b2e5465f21d059ea08537012e140236@eucas1p1.samsung.com>
2020-01-09 15:41 ` Daniel Shahaf [this message]
2020-01-09 15:51 ` Peter Stephenson
2020-01-09 16:10 ` Bart Schaefer
2020-01-09 16:16 ` Daniel Shahaf
[not found] ` <1578585101.6028.13.camel__24021.2781982095$1578585228$gmane$org@samsung.com>
2020-01-09 17:22 ` Stephane Chazelas
2020-01-09 23:05 ` Mikael Magnusson
2020-01-10 17:11 ` Daniel Shahaf
[not found] ` <20200109172222.uwgyjouab45zk2gf__13897.4118557357$1578604026$gmane$org@chaz.gmail.com>
2020-01-10 7:27 ` Stephane Chazelas
2020-01-10 17:09 ` Daniel Shahaf
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=20200109154145.rqksfenozx6745rn@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=zsh-users@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).