From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Unreadable directories aren't included in glob expansion
Date: Thu, 9 Jan 2020 08:10:50 -0800 [thread overview]
Message-ID: <CAH+w=7bhY0omAjp8ngGKtx8t3mG65L9KmnVfZEFLfwo6tXEiKA@mail.gmail.com> (raw)
In-Reply-To: <1578585101.6028.13.camel@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
On Thu, Jan 9, 2020, 7:52 AM Peter Stephenson <p.stephenson@samsung.com>
wrote:
>
> At a practical level, the difference may have arisen because a / not in
> a glob qualifier is usually present in order to select files within the
> directory, which won't work if the directory isn't readable. A glob
> qualifier, on the other hand, always applies to the final path segment.
>
I think this is exactly it. foo/<TAB> is like asking to select from among
the matches of foo/* and if foo is not readable, there are none.
next prev parent reply other threads:[~2020-01-09 16:11 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 [this message]
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='CAH+w=7bhY0omAjp8ngGKtx8t3mG65L9KmnVfZEFLfwo6tXEiKA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=p.stephenson@samsung.com \
--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).