From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-37688-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 28660 invoked by alias); 19 Jan 2016 09:36:57 -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>
X-Seq: 37688
Received: (qmail 13150 invoked from network); 19 Jan 2016 09:36:55 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.0
X-AuditID: cbfec7f4-f79026d00000418a-00-569e03b3ff2e
Date: Tue, 19 Jan 2016 09:36:49 +0000
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: bufferwords() lexes a subshell in a shortloop repeat as a string
Message-id: <20160119093649.53d5c7b9@pwslap01u.europe.root.pri>
In-reply-to: <160118163255.ZM3369@torch.brasslantern.com>
References: <20160115062648.GA14019@tarsus.local2>
 <20160115094117.5fcde75c@pwslap01u.europe.root.pri>
 <160115112516.ZM21347@torch.brasslantern.com>
 <20160117181647.49899357@ntlworld.com>
 <160117144635.ZM3583@torch.brasslantern.com>
 <20160118094129.260a60ae@pwslap01u.europe.root.pri>
 <160118083658.ZM6465@torch.brasslantern.com>
 <20160118165237.11b1349a@pwslap01u.europe.root.pri>
 <160118163255.ZM3369@torch.brasslantern.com>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsVy+t/xy7qbmeeFGRy8J2lxsPkhkwOjx6qD
	H5gCGKO4bFJSczLLUov07RK4Mlp2dTAXfGKvWLX2JlMD43S2LkZODgkBE4kvh1YyQthiEhfu
	rQeKc3EICSxllHi99T8LhDODSeLVzV6ozDlGieb93UwQzllGiWM3r4LNYhFQlfg7bSUziM0m
	YCgxddNssLkiAuISZ9eeZwGxhQV8JSb1H2cHsXkF7CU2rLoFVs8pYCnx8OlDZoihu5gl9k9q
	ZgVJ8AvoS1z9+4kJ4kB7iZlXzjBCNAtK/Jh8D2wos4CWxOZtTawQtrzE5jVvwYYKCahL3Li7
	m30Co/AsJC2zkLTMQtKygJF5FaNoamlyQXFSeq6hXnFibnFpXrpecn7uJkZISH/Zwbj4mNUh
	RgEORiUe3gn2c8OEWBPLiitzDzFKcDArifAK/AEK8aYkVlalFuXHF5XmpBYfYpTmYFES5527
	632IkEB6YklqdmpqQWoRTJaJg1OqgdHfI/Wobyrrk2KRYLs/H9I7Qg7+qn/7+E9t0elt6ioi
	BfbGCtbeZTwPVC7szDZTmc/Y8dZp07fF7YHL5y9ZZ7wjn2OX3ozQvdY7ZSbuUsvxe6B8d0Kk
	/rzt7LPYDcRuHfr5c7sXzzrVn+wN2lPzbWu1mWrcA/ve3n0YLsXz9bbfr83befyOKimxFGck
	GmoxFxUnAgBEAggcZQIAAA==

On Mon, 18 Jan 2016 16:32:55 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> Directly at command line, gettok() returns "\210two three\216four\212".
> 
> Does the below look correct?

It's certainly plausible.

> Aside:  "emulate sh" does the equivalent of
> 
>     setopt shglob noglob nokshglob
> 
> In order to make kshglob work, one must
> 
>     setopt glob kshglob
> 
> Is that correct, or should only kshglob be needed?

Do you really mean "glob"/"noglob"?  I thought that meant what it says,
controlling all globbing.  I can't see any evidence it's related to
emulation --- it's got the "emulate" attribute, so is affected by
"emulate" without -R but it's on in all emulations.  (Not sure what use
that combination is... Oh, I see, if you turned it off yourself for some
reason, then as soon as you try to set up for any standard emulation it
goes back on again.)

I think the real question is whether kshglob should actually be on in sh
emulation nowadays.

pws