From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: padding.
Date: Mon, 13 Feb 2017 13:58:37 -0800 [thread overview]
Message-ID: <123535f0-62f3-3e32-3e83-d1c98d8eb7d9@eastlink.ca> (raw)
In-Reply-To: <20170212061455.GA4267@fujitsu.shahaf.local2>
On 11/02/17 10:14 PM, Daniel Shahaf wrote:
>
> % if false; then if true; fi
> % setopt noshortloops
> % if false; then if true; fi
> zsh: parse error near `fi'
>
> I'm guessing the second 'if' is parsed using the SHORT_LOOPS syntax,
> with an empty sublist. I'm not sure whether that's a bug: is the
> sublist in the SHORT_LOOPS syntax allowed to be null?
Well no one else has commented on it, but I don't know how it could not
be a bug, tho this 'shortloops' must be there for a reason. Docs refer
to the 'short form' of various constructs but what's the point of it
here? I see the use with 'while', but with 'if' it seems trivial. I
see it as just letting me get away with mistakes.
>
>> and:
>>
>> $ if [ "$1" = "start" ]; then
>> # if [ "$1" = 'null' ] && return
>> fi
>>
>> (no message)
> That's expected.
Yes, it's just there as contrast for the questionable one.
next prev parent reply other threads:[~2017-02-13 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 3:15 padding Ray Andrews
2017-02-11 19:04 ` padding Bart Schaefer
2017-02-12 1:54 ` padding Ray Andrews
2017-02-12 2:11 ` padding Ray Andrews
[not found] ` <ee3c8ad2-41e3-f3e4-9347-d6e395b85d8e__47549.2452657365$1486864527$gmane$org@eastlink.ca>
2017-02-12 6:14 ` padding Daniel Shahaf
2017-02-12 20:10 ` padding Ray Andrews
2017-02-13 21:58 ` Ray Andrews [this message]
[not found] ` <CAHYJk3SKvOSOBgK6GTVnbqL1mJ7mnwchoAbVKjjNRE8FjFWNYQ@mail.gmail.com>
2017-02-14 5:51 ` padding Ray Andrews
[not found] <0befdb38-eaa5-6388-a3fe-58b1a73834b7__26816.8318471455$1486784821$gmane$org@eastlink.ca>
2017-02-11 6:29 ` padding Daniel Shahaf
2017-02-11 18:43 ` padding Ray Andrews
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=123535f0-62f3-3e32-3e83-d1c98d8eb7d9@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).