From: Roman Neuhauser <neuhauser@sigpipe.cz>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@zsh.org
Subject: Re: globbing in conditional expressions
Date: Thu, 8 May 2014 22:19:36 +0200 [thread overview]
Message-ID: <20140508201936.GB53652@isis.sigpipe.cz> (raw)
In-Reply-To: <140508083418.ZM14713@torch.brasslantern.com>
# schaefer@brasslantern.com / 2014-05-08 08:34:18 -0700:
> On May 8, 12:20pm, Peter Stephenson wrote:
> }
> } > All three solutions first set an array to the result of the glob. Is
> } > there a solution that short-circuits, i.e., that returns as soon as a
> } > single matching filename is found?
> }
> } No, unless someone remembers I feature I don't know about, because
> } internally the glob proceeds until it's finished
>
> Well ... you can do this horrible hack:
>
> found=
> # Stop after finding exactly one directory, for example:
> : **/*(e+'[[ -d $REPLY ]] && { found=$REPLY ; kill -INT $$ }'+)
> print $found
>
> Of course to make this "useful" all the stuff that you'd test in the
> glob qualifiers you instead need to test in the [[ ... ]] before you
> assign found=$REPLY, probably by using the zsh/stat module; and you
> can't avoid scanning an unknown number of potential NON-matches up
> to the point where $found gets set, so in the worst case it's no
> better (and probably much worse) than just letting the glob finish.
maybe a crazy idea... how about something like [[ -m pattern ]] which
would succeed iff pattern matched at least one path? this could be
somewhat more amenable to shortcircuiting.
--
roman
next prev parent reply other threads:[~2014-05-08 20:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 12:41 Roman Neuhauser
2014-05-07 14:44 ` Peter Stephenson
2014-05-08 10:55 ` Daniel Shahaf
2014-05-08 11:20 ` Peter Stephenson
2014-05-08 15:34 ` Bart Schaefer
2014-05-08 20:19 ` Roman Neuhauser [this message]
2014-05-13 15:41 ` Bart Schaefer
2014-05-14 4:19 ` Daniel Shahaf
2014-05-14 7:18 ` Bart Schaefer
2014-05-15 4:55 ` Bart Schaefer
2014-05-15 9:35 ` Daniel Shahaf
2014-05-15 14:33 ` Bart Schaefer
2014-05-15 9:29 ` Daniel Shahaf
2014-05-15 14:50 ` Bart Schaefer
2014-05-26 23:52 ` Daniel Shahaf
2014-05-30 3:59 ` Bart Schaefer
2014-05-30 8:47 ` Peter Stephenson
2014-05-30 15:55 ` Bart Schaefer
2014-05-31 4:43 ` Bart Schaefer
2014-05-31 17:34 ` Daniel Shahaf
2014-05-31 17:59 ` Bart Schaefer
2014-06-02 9:40 ` Peter Stephenson
2014-06-02 12:57 ` Daniel Shahaf
2014-06-02 14:15 ` Peter Stephenson
2014-05-30 14:45 ` Daniel Shahaf
2014-05-14 7:42 ` Christoph (Stucki) von Stuckrad
2014-05-14 21:09 ` Roman Neuhauser
2014-05-15 9:14 ` Daniel Shahaf
2014-05-15 10:05 ` Roman Neuhauser
2014-05-07 14:57 ` Mikael Magnusson
2014-05-07 15:03 ` Bart Schaefer
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=20140508201936.GB53652@isis.sigpipe.cz \
--to=neuhauser@sigpipe.cz \
--cc=schaefer@brasslantern.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).