From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-users@zsh.org
Subject: Re: Unreadable directories aren't included in glob expansion
Date: Fri, 10 Jan 2020 17:11:32 +0000 [thread overview]
Message-ID: <20200110171132.ag4zizy3ifjnmx2u@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <20200109172222.uwgyjouab45zk2gf@chaz.gmail.com>
Stephane Chazelas wrote on Thu, Jan 09, 2020 at 17:22:22 +0000:
> Now, zsh seems to be the only shell where */ excludes the
> non-*searchable* (it does include the non-readable ones provided
> you have search access).
>
> It might make it the only POSIX compliant shell as I have a
> vague recollection it's meant to give the same result as */.,
> but that could very well be a bad recollection, and if that was
> a POSIX requirement, that's probably one that should change.
So there isn't any need to make the bugfix conditional on some POSIX_* option
being unset, right?
> IMO, */ should give the same list as *(-/) (with some /
> appended), that is expand to the files that can be determined to
> be of type "directory" after symlink resolution (determined from
> the result of stat(), not lstat()) for consistency with other
> shells.
Cheers,
Daniel
next prev parent reply other threads:[~2020-01-10 17:12 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
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 [this message]
[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=20200110171132.ag4zizy3ifjnmx2u@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).