From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-23035-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 12140 invoked by alias); 30 Dec 2017 17:52:32 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
List-Unsubscribe: <mailto:zsh-users-unsubscribe@zsh.org>
X-Seq: 23035
Received: (qmail 1787 invoked by uid 1010); 30 Dec 2017 17:52:32 -0000
X-Qmail-Scanner-Diagnostics: from mta02.eastlink.ca by f.primenet.com.au (envelope-from <rayandrews@eastlink.ca>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(24.224.136.13):SA:0(-2.6/5.0):. 
 Processed in 1.935942 secs); 30 Dec 2017 17:52:32 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,
	SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham autolearn_force=no version=3.4.1
X-Envelope-From: rayandrews@eastlink.ca
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: text/plain; charset=utf-8; format=flowed
X-Authority-Analysis: v=2.3 cv=dfKuI0fe c=1 sm=1 tr=0
 a=RnRVsdTsRxS/hkU0yKjOWA==:117 a=RnRVsdTsRxS/hkU0yKjOWA==:17 a=IkcTkHD0fZMA:10
 a=q2GGsy2AAAAA:8 a=RNfS0oskB0YRdJlpfHsA:9 a=QEXdDO2ut3YA:10
 a=z9dJwno5l634igLiVhy-:22
X-EL-IP-NOAUTH: 24.207.101.9
Subject: Re: Can zsh `else` reserved keyword command be aliased and the lexem
 itself be repurposed as `fi` keyword command?
To: zsh-users@zsh.org
References: <ecebd27c-08ad-7cb3-50a9-d6ba56e288ef@epopia.com>
 <ef2c2e74-8f03-bfcb-1dd9-bfb1594c8b40@culture-libre.org>
 <CAH+w=7Ynbar1=vZsNkBK6Ae1HXN2jJRNTVd9Ce=1JyUsZepqLA@mail.gmail.com>
 <71ef7896-39f8-66fe-f8f8-c7c81b11e2ce@culture-libre.org>
 <CAH+w=7b=0c4Vd4SuNXX=czcp8KBOev6vZTUjpm2qokk4oCE6cA@mail.gmail.com>
 <918acbfa-b637-1d13-816b-c6edee0afa5c@culture-libre.org>
 <CAH+w=7a4otey0NRRORXmqceZ242rnQ3C4=qYY76wh1R-XgUvcQ@mail.gmail.com>
 <81beaeae-6507-c961-b6fd-5831ba58e045@eastlink.ca>
 <CAH+w=7ar+MYVEHXPuFOMAQp0N4sr4N9JS4YXRz1707OPMQ4FMQ@mail.gmail.com>
 <CAH+w=7bO1pdonnpVoYv8E0Yj9ASSegAZWqR3QHt5yiicMSLT_g@mail.gmail.com>
From: Ray Andrews <rayandrews@eastlink.ca>
Message-id: <d7a6b0f1-de8e-a3d4-5129-3d7aea366321@eastlink.ca>
Date: Sat, 30 Dec 2017 09:22:24 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
In-reply-to:
 <CAH+w=7bO1pdonnpVoYv8E0Yj9ASSegAZWqR3QHt5yiicMSLT_g@mail.gmail.com>
Content-language: en-CA

On 29/12/17 05:07 PM, Bart Schaefer wrote:
> 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.
> 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.
>
Cool!  These insights from history are so very illuminating.  Mind ... 
that would seem to make it all the more possible/acceptable to do what 
Mathieu wants, it'd be a compatibility featurenot some sort of 
abominable novelty the way my suggestions are abominable novelties.


setopt csh_parsing ?