Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160117144635.ZM3583@torch.brasslantern.com>
Date: Sun, 17 Jan 2016 14:46:35 -0800
In-Reply-To: <20160117181647.49899357@ntlworld.com>
Comments: In reply to Peter Stephenson <p.w.stephenson@ntlworld.com>
        "Re: bufferwords() lexes a subshell in a shortloop repeat as a string" (Jan 17,  6:16pm)
References: <20160115062648.GA14019@tarsus.local2> 
	<20160115094117.5fcde75c@pwslap01u.europe.root.pri> 
	<160115112516.ZM21347@torch.brasslantern.com> 
	<20160117181647.49899357@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: bufferwords() lexes a subshell in a shortloop repeat as a string
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Jan 17,  6:16pm, Peter Stephenson wrote:
} Subject: Re: bufferwords() lexes a subshell in a shortloop repeat as a str
}
} On Fri, 15 Jan 2016 11:25:16 -0800
} Bart Schaefer <schaefer@brasslantern.com> wrote:
} > On Jan 15,  9:41am, Peter Stephenson wrote:
} > } Subject: Re: bufferwords() lexes a subshell in a shortloop repeat as a str
} > }
} > } it's just splitting words, and (... ...) indeed works as a complete word
} > 
} > Urk.  That probably ought to be disabled, at least in shell emulation,
} > e.g. here is bash:
} 
} shwordsplit does this.  (I thought it would be shglob, but it isn't.)

Hrm.  I see no evidence of that.

Src/zsh -f

torch% emulate sh 
torch% print -l one (two three) four
one
(two three)
four
torch% 

ARGV0=sh Src/zsh

$ print -l one (two three) four
one
(two three)
four
$ 

It appears that parens are still parsed as grouping, even though they
thereafter are considered a literal pattern character.  E.g., I expected
"|" to be treated as a pipe in the following:

$ print -l one (two three|foo) four
one
(two three|foo)
four