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: Fri, 29 Dec 2017 12:27:51 -0800 [thread overview]
Message-ID: <81beaeae-6507-c961-b6fd-5831ba58e045@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7a4otey0NRRORXmqceZ242rnQ3C4=qYY76wh1R-XgUvcQ@mail.gmail.com>
On 29/12/17 11:49 AM, Bart Schaefer wrote:
> On Fri, Dec 29, 2017 at 11:29 AM, mathieu stumpf guntz
> <psychoslave@culture-libre.org> wrote:
>> The question is not to know if the interpreter can execute an incomplete
>> program. The point is to send a signal to the interpreter which order to
>> interrupt usual parsing and try to interpret what was already buffered right
>> now.
> Of course from the command line (as opposed to when reading a script
> file) that *is* what happened. However, the result of "try to
> interpret" was "oh, this isn't complete yet, I need to ask for the
> rest".
>
As for me, the very idea that a reserved word could be aliased seems
monstrous. In any information system there must be tokens who's meaning
is absolute. How you guys can begin to make it possible to parse such
things is beyond me, it seems like black magic. But I am curious, what
does it mean to say that an interpreted program is incomplete? I mean,
unclosed quotes and such things are clearly incomplete, but other than that?
next prev parent reply other threads:[~2017-12-29 20:57 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 [this message]
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
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=81beaeae-6507-c961-b6fd-5831ba58e045@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).