From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: zsh-workers-return-43603-ml=inbox.vuxu.org@zsh.org
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham
	autolearn_force=no version=3.4.2
Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2])
	by inbox.vuxu.org (OpenSMTPD) with ESMTP id bdf8679b
	for <ml@inbox.vuxu.org>;
	Thu, 4 Oct 2018 20:04:54 +0000 (UTC)
Received: (qmail 7970 invoked by alias); 4 Oct 2018 20:04:40 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
List-Unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
X-Seq: 43603
Received: (qmail 10372 invoked by uid 1010); 4 Oct 2018 20:04:40 -0000
X-Qmail-Scanner-Diagnostics: from aurora-borealis.phear.org by f.primenet.com.au (envelope-from <eiro@phear.org>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(94.242.205.164):SA:0(-1.9/5.0):. 
 Processed in 4.328141 secs); 04 Oct 2018 20:04:40 -0000
X-Envelope-From: eiro@phear.org
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
X-Virus-Scanned: amavisd-new at phear.org
DKIM-Filter: OpenDKIM Filter v2.10.3 aurora-borealis.phear.org 5365E106B1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=phear.org;
	s=20180217; t=1538683467;
	bh=uPNitpqeVxmTsmim4AvD8xpbf9V937YmSazpNMVlD0w=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=lg5fbeh5Pg8PmknDeSQ4oCa0IGgQrrzF6NcKZygyV4zUjlpuGHvEMi3z0SovhfpmL
	 iquj89g8a2s1tzEsRUbo1HcmegB0kiF/fGdzmIzbS7/Niq2K9x4/a8Eat6jJ3DLGMV
	 Y6Q2YQ/Ss75UMEAdaCV1xSHFmk9poYce/qVyJGhPYHWcnoMp25fj4zmfHHZIywASM6
	 3eG+flrmAx2v1Wwq+7Zjirnzu7gfEhjkafDx/Aqr/4FaQtoaAwIjDtHp6ypPoJS0OB
	 xo1rvsvijWULd3gtCGmJJVzvMeOQW5B+GGcjXAly3bhb+Jh8ALMRJWa6NXPO4J9sj6
	 WpD5lqp1xjhsA==
Date: Thu, 4 Oct 2018 22:04:25 +0200
From: Marc Chantreux <eiro@phear.org>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh-workers@zsh.org
Subject: Re: Parse error (lack thereof) on incomplete loops
Message-ID: <20181004200425.GA23515@prometheus.u-strasbg.fr>
References: <CGME20181004154947epcas4p2441e109a2c4e060bf39f0f6925e98241@epcas4p2.samsung.com>
 <CAH+w=7awbwDuX2RXcB7pK6Hhbi8fjs=NvwkTAEGmY7gvNpLCqA@mail.gmail.com>
 <20181004163158eucas1p234a045be013b5463d8db44314ed217dc~adN28lJmq0822408224eucas1p2F@eucas1p2.samsung.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20181004163158eucas1p234a045be013b5463d8db44314ed217dc~adN28lJmq0822408224eucas1p2F@eucas1p2.samsung.com>
User-Agent: Mutt/1.10.1 (2018-07-13)

hello Peter,

Again: thanks for your amazing job Bart and you did on zsh.

> However, I'm very far from convinced this is actually a bug.  If you
> turn off SHORT_LOOPS you'll find you get the error back; the

is there a way to turn it off from configuration? it looks like an
option in the manual but

    setopt noshortloop

gives me

    setopt: no such option: noshortloop

> I'm therefore inclined to leave it alone since the SHORT_LOOPS user
> (Marc) is perfectly happy with it and a lot of us avoid the alternative
> syntax like the plague.

is it just because people don't like it or are there technical reasons
to avoid it?

regards