From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Can zsh `else` reserved keyword command be aliased and the lexem itself be repurposed as `fi` keyword command?
Date: Sat, 30 Dec 2017 15:00:14 -0800 [thread overview]
Message-ID: <0206889d-5088-4604-0f89-80ea23a7b43f@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7Yy1AGQzCri2AQn5sMQe3mCaw7QVzBc3PcnBrDG9MyctQ@mail.gmail.com>
On 30/12/17 02:06 PM, Bart Schaefer wrote:
>
> You really don't want to go there.
>
> If you're desperate to experience something like this,
Heck no, not me, I'm just interested in the zen of the idea. And you've
already said enough for me to understand that some naive idea about a
'csh' mode is a nonstarter.
Yabut, what about some sort of auto-ending of code structures? Even if
parsing was by exactly the same non-csh method, would it not be possible
to turn off the code checker and just sorta run until the tracks stop at
which point the thing returns?
if [ something ]; then blah
elif [something_else]; then foo
... and it just stops there not worrying about the fact that 'fi' is
missing.
Or, does the zsh parsing system really forbid such a thing? True, it
would know about the issue at the parse and before execution even
begins, but could it not just 'presume' the 'fi'? Sorta like the fact
that I should close the door after I leave, but it is possible for me to
depart and leave the door open. Mind, this could only even theoretically
apply to code that is missing closings at the very end of itself. Maybe
easier to imagine than to implement, and certainly rather strange.
Never mind, I'm just curious.
next prev parent reply other threads:[~2017-12-30 23:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 15:07 mathieu stumpf guntz
2017-12-28 15:19 ` mathieu stumpf guntz
2017-12-29 8:47 ` Bart Schaefer
2017-12-29 10:51 ` mathieu stumpf guntz
2017-12-29 19:15 ` Bart Schaefer
2017-12-29 19:29 ` mathieu stumpf guntz
2017-12-29 19:49 ` Bart Schaefer
2017-12-29 20:27 ` Ray Andrews
2017-12-29 23:45 ` Bart Schaefer
2017-12-30 1:07 ` Bart Schaefer
2017-12-30 9:50 ` mathieu stumpf guntz
2017-12-30 10:05 ` Frank Terbeck
2017-12-30 17:22 ` Ray Andrews
2017-12-30 22:06 ` Bart Schaefer
2017-12-30 23:00 ` Ray Andrews [this message]
2017-12-30 17:16 ` Ray Andrews
2017-12-30 22:23 ` mathieu stumpf guntz
2017-12-30 23:06 ` Ray Andrews
2017-12-30 23:32 ` mathieu stumpf guntz
2017-12-30 9:36 ` mathieu stumpf guntz
2017-12-30 17:39 ` Ray Andrews
2017-12-29 22:59 ` Nikolay Aleksandrovich Pavlov (ZyX)
2017-12-29 8:38 ` Bart Schaefer
2017-12-29 10:24 ` mathieu stumpf guntz
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=0206889d-5088-4604-0f89-80ea23a7b43f@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).