From: Ray Andrews <rayandrews@eastlink.ca>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: for loop question
Date: Mon, 03 Nov 2014 09:26:47 -0800 [thread overview]
Message-ID: <5457BAD7.8040004@eastlink.ca> (raw)
In-Reply-To: <CAHYJk3T4=8fxBKFKJ_7ppLWrNPd4sV9kd9Jss3=f8WihwwgXXQ@mail.gmail.com>
On 11/03/2014 01:22 AM, Mikael Magnusson wrote:
> If you look up the section "Complex Commands" in the manpage, they're
> all listed fairly well explained. ...
Thanks. You know, with so many documents available, it's hard to know
what it worth
reading. I wish there was a sort of recommended list of docs and web
sites so that one
wouldn't waste so much time looking for things worth reading. I have
Oliver's book
here, and at least I know it's approved.
> As to the for loop, it has two different forms. They're almost so
> different you could say the only thing they have in common is the word
> "for" :). One is
Just those three lines might save a fella hours of grief. I intuitively
expect them to be
related *and* to be related to the C form, which explains my head
banging over:
for ((i = 1; [ -n ${TLC[i] ]; i++))
... because in C one can always test for the return value of anything at
all and it looks so
very much like C.
for ((i=1; (z[$([ -n "$TLC[i]" ])0]),$? == 0; i++))
... is sick and twisted, but:
for ((i = 1; $#TLC[i]; i++))
... is sweetly, intuitively best anyway.
> As a side note, if you ever want a do-while loop instead of a regular
> while loop, the trick is
> while just put the whole body;
> of the loop here instead;
> and the last command is;
> the terminating condition; do done
Marvelous, I was wondering about that.
If I ever master zsh I'd like to write an essay: "Zsh culture for the
sweet and innocent: Truths you hold to be self-evident that aren't true
any more, or the weltanschauung of weltschmertz"
next prev parent reply other threads:[~2014-11-03 16:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 20:47 Ray Andrews
2014-11-02 21:00 ` Bart Schaefer
[not found] ` <CAH+w=7aWS0xyS4CXRJBphDjesfUFQOsyJRMaG3RZRxmuj7xkOg__20885.3257158355$1414962125$gmane$org@mail.gmail.com>
2014-11-02 21:37 ` Stephane Chazelas
2014-11-02 22:44 ` Ray Andrews
2014-11-02 22:57 ` Bart Schaefer
2014-11-02 23:24 ` Oliver Kiddle
2014-11-03 0:07 ` Ray Andrews
2014-11-03 1:53 ` Mikael Magnusson
2014-11-03 2:22 ` Ray Andrews
2014-11-03 9:22 ` Mikael Magnusson
2014-11-03 17:26 ` Ray Andrews [this message]
2014-11-04 1:56 ` Han Pingtian
2014-11-04 2:29 ` Han Pingtian
2014-11-04 2:43 ` Bart Schaefer
2014-11-04 4:51 ` Han Pingtian
2014-11-04 6:37 ` Ray Andrews
2014-11-04 7:13 ` Bart Schaefer
2014-11-04 18:00 ` Ray Andrews
[not found] ` <141103184338.ZM32221__48957.5251042426$1415069142$gmane$org@torch.brasslantern.com>
2014-11-04 7:08 ` Stephane Chazelas
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=5457BAD7.8040004@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=mikachu@gmail.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).