zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Tests for globbing below protected directories
Date: Wed, 3 Feb 2021 14:33:28 -0800	[thread overview]
Message-ID: <CAH+w=7b81vX7pT2nQt9PuybOLG8n6d3npTe31NRMiGvgaQZUJA@mail.gmail.com> (raw)
In-Reply-To: <20210203112225.GB12261@tarpaulin.shahaf.local2>

On Wed, Feb 3, 2021 at 3:22 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Sorry I wasn't clear.  I was observing that the expansion of «*/*» does not
> include «foo/bar», even though the expansion of «*/bar» does include «foo/bar»
> and one might expect the expansion of «*/*» to be a superset of the expansion of
> «*/bar».  This could be surprising.

Perhaps, but that's the definition of the difference between
"readable" and "searchable" (executable) directories.  In the example
of «foo/bar», if the parent of foo is searchable but foo is only
readable, then you can expand «*» to discover foo and attempt to
"read" under «foo/» for the existence of the known name bar, but you
can't "search" foo (expand «foo/*») to discover anything, so by
extension «*/*» can't include «foo/bar».


  reply	other threads:[~2021-02-03 22:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25  0:15 Bart Schaefer
2021-01-26 23:56 ` Daniel Shahaf
2021-02-02  2:45   ` Bart Schaefer
2021-02-03 11:22     ` Daniel Shahaf
2021-02-03 22:33       ` Bart Schaefer [this message]
2021-02-03 23:06         ` Bart Schaefer
2021-02-04 13:09           ` Daniel Shahaf
2021-02-04 21:34             ` Bart Schaefer
2021-02-06 12:15               ` 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=7b81vX7pT2nQt9PuybOLG8n6d3npTe31NRMiGvgaQZUJA@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=d.s@daniel.shahaf.name \
    --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).