zsh-users
 help / color / mirror / code / Atom feed
From: mathieu stumpf guntz <psychoslave@culture-libre.org>
To: Bart Schaefer <schaefer@brasslantern.com>, Zsh Users <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 10:50:37 +0100	[thread overview]
Message-ID: <3326ffbc-e1ef-cb5a-124c-6597c50cd053@culture-libre.org> (raw)
In-Reply-To: <CAH+w=7bO1pdonnpVoYv8E0Yj9ASSegAZWqR3QHt5yiicMSLT_g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]


Le 30/12/2017 à 02:07, Bart Schaefer a écrit :
> On Fri, Dec 29, 2017 at 3:45 PM, Bart Schaefer
> <schaefer@brasslantern.com> wrote:
>> Mathieu wants execution to begin as soon as there is
>> some code in the buffer, without waiting for the final keyword to
>> appear.
Where odes this quote come from, it seems I missed a message. Did 
someone replied to "zsh-workers@"?

> Not-so-incidentally, the fact that zsh does NOT do this is one of the
> primary reasons that zsh exists at all.  Paul Falstad found it
> distasteful that csh DOES that, and set out to create a shell that had
> the interactive advantages of csh while preserving the separation of
> parse and execution as found in sh and ksh.
I was, of course, completely unaware of that. I would be interested with 
more technical details if you could provide me some links.

And, just for memory, forcing execution at some explicit point is not my 
goal, but just a possible mean I considered to bypass the lake of a 
"keyword" reserved-keyword-command, similar to `command` and `builtin`. 
Implenting such a thing wouldn't require de abandon the separation of 
parse and execution, would it?

Cheers

  reply	other threads:[~2017-12-30  9:50 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 [this message]
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=3326ffbc-e1ef-cb5a-124c-6597c50cd053@culture-libre.org \
    --to=psychoslave@culture-libre.org \
    --cc=schaefer@brasslantern.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).