From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: &&||
Date: Mon, 19 Feb 2018 23:54:38 -0800 [thread overview]
Message-ID: <ba9a569c-9462-0062-8630-ddc3bab1b1e3@eastlink.ca> (raw)
In-Reply-To: <20180220092659.2233e6ef@pwslap01u.europe.root.pri>
On 20/02/18 01:26 AM, Peter Stephenson wrote:
> I think you were trying to make the status depend only on what was
> before the first "&&". You can certainly do
But isn't that exactly what I did do? Appending to you code below:
> first-statement && {
> any-old-stuff
> } || {something-else-entirely}
Yet the return value of any-old-stuff (egrep in practice) was what
actually controlled something-else-entirely. I'm not expecting the
pipes within any braced structure to make any difference. Is that
what's happening? Is so, how/why? Do not the braces pointedly force
the entire structure to be subordinate to the first '&&'? It seems to
me that the left>right association in my original code is sorta
'brutally' adhered to in such a way that the natural meaning of the
braces is violated such that any-old-stuff has control of branching when
the natural logic is that first-statement has it. Yes? No?
if first-statement; then
{ any-old-stuff}
else
{something-else-entirely}
fi
That works fine egrep and/or pipes notwithstanding, yet I'm expecting
both to work the same. You seem to suggest they should as well.
next prev parent reply other threads:[~2018-02-20 16:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 21:12 &&|| Ray Andrews
2018-02-19 21:57 ` &&|| Peter Stephenson
2018-02-19 22:47 ` &&|| Ray Andrews
2018-02-20 9:26 ` &&|| Peter Stephenson
2018-02-20 7:54 ` Ray Andrews [this message]
2018-02-20 17:07 ` &&|| Peter Stephenson
2018-02-20 19:24 ` &&|| Ray Andrews
2018-02-20 20:28 ` &&|| Bart Schaefer
2018-02-20 21:45 ` &&|| Ray Andrews
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 13:45 !!:$ keef
2004-11-16 14:22 ` !!:$ Peter Stephenson
2004-11-16 14:31 ` !!:$ Stephane Chazelas
2004-11-16 15:37 ` !!:$ Bart Schaefer
2004-11-16 16:08 ` !!:$ Peter Stephenson
2004-11-17 0:03 ` !!:$ Bart Schaefer
2004-11-17 19:25 ` !!:$ Danek Duvall
2004-11-18 1:10 ` !!:$ Bart Schaefer
2003-07-02 15:06 ?????? JEFF BICKLEY
2003-07-02 19:56 ` ?????? Thorsten Haude
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=ba9a569c-9462-0062-8630-ddc3bab1b1e3@eastlink.ca \
--to=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).