Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160115112516.ZM21347@torch.brasslantern.com>
Date: Fri, 15 Jan 2016 11:25:16 -0800
In-Reply-To: <20160115094117.5fcde75c@pwslap01u.europe.root.pri>
Comments: In reply to Peter Stephenson <p.stephenson@samsung.com>
        "Re: bufferwords() lexes a subshell in a shortloop repeat as a string" (Jan 15,  9:41am)
References: <20160115062648.GA14019@tarsus.local2> 
	<20160115094117.5fcde75c@pwslap01u.europe.root.pri>
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 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:

schaefer@burner$ echo one (two three) four
bash: syntax error near unexpected token `('

Here's an interesting side effect:

torch% touch "two three"
torch% unsetopt bareglobqual
torch% ls -l (two three)
-rw-rw-r--  1 schaefer schaefer 0 Jan 15 11:22 two three

It becomes another way to quote spaces in file names, but only if the file
already exists.

torch% touch (one two)
zsh: no matches found: (one two)