zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Lawrence Velázquez" <larryv@zsh.org>
Cc: Ray Andrews <rayandrews@eastlink.ca>, zsh-users@zsh.org
Subject: Re: unintuitive bracketing with return value
Date: Tue, 18 Oct 2022 13:12:20 -0700	[thread overview]
Message-ID: <CAH+w=7Yxz9hALOiEXStadYiSNtvarLTx+Pv64+BJxn8-5te59g@mail.gmail.com> (raw)
In-Reply-To: <a405d914-2be3-4e2e-bcbc-dae43864d162@app.fastmail.com>

On Tue, Oct 18, 2022 at 12:33 PM Lawrence Velázquez <larryv@zsh.org> wrote:
>
> On Tue, Oct 18, 2022, at 1:57 PM, Ray Andrews wrote:
> > Very well written!  What breaks my intuition tho is the brackets.
> > Otherwise I quite understand that the last exit value is the active
> > one.  I'm expecting the brackets to 'contain' the rv of any commands
> > within the brackets.  But no, the left > right rule applies and the
> > brackets don't make any difference.
>
> I don't understand why you keep saying this.  Without the braces
> your command would be completely different.

I think Ray's just got the opening bracket in the wrong place.  He's
describing the bracketing as if it were this:

{ "${${1}##*[*?]*}" ] &&
echo "no wildcards"; printenv "$1" } || echo wildcards present

which would do exactly what he wants.


  reply	other threads:[~2022-10-18 20:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 14:47 Ray Andrews
2022-10-18 14:57 ` Eric Cook
2022-10-18 17:57   ` Ray Andrews
2022-10-18 19:32     ` Lawrence Velázquez
2022-10-18 20:12       ` Bart Schaefer [this message]
2022-10-18 20:14         ` Bart Schaefer
2022-10-18 20:22       ` Ray Andrews
2022-10-18 20:31         ` Clinton Bunch
2022-10-18 16:07 ` Roman Perepelitsa

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=7Yxz9hALOiEXStadYiSNtvarLTx+Pv64+BJxn8-5te59g@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=larryv@zsh.org \
    --cc=rayandrews@eastlink.ca \
    --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).