From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-31450-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 5731 invoked by alias); 3 Jun 2013 15:31:56 -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: 31450
Received: (qmail 28114 invoked from network); 3 Jun 2013 15:31:50 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	SPF_HELO_PASS autolearn=ham version=3.3.2
Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts)
X-AuditID: cbfec7f5-b7f376d000001ec6-b9-51acb6e1c6b3
Date: Mon, 03 Jun 2013 16:31:44 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: PATCH: configurability of pattern characters, part 1
Message-id: <20130603163144.34ef0219@pwslap01u.europe.root.pri>
In-reply-to:
 <CAH+w=7advMYcjCGL1yvZN2BvBV1iN20Nnm0jsoQ+UXQuJ1RiOg@mail.gmail.com>
References: <20130601002954.0e30d7b9@pws-pc.ntlworld.com>
 <130531232223.ZM13592@torch.brasslantern.com>
 <20130601211836.550bd8ac@pws-pc.ntlworld.com>
 <130602001627.ZM15649@torch.brasslantern.com>
 <20130603094014.4728e466@pwslap01u.europe.root.pri>
 <CAH+w=7advMYcjCGL1yvZN2BvBV1iN20Nnm0jsoQ+UXQuJ1RiOg@mail.gmail.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+NgFuphluLIzCtJLcpLzFFi42I5/e/4Zd2H29YEGjxYI2xxsPkhkwOjx6qD
	H5gCGKO4bFJSczLLUov07RK4Mq7e2M9ccJm5ov33P8YGxq9MXYycHBICJhKta2azQ9hiEhfu
	rWfrYuTiEBJYyihxesFLKGc5k8SXb8fBqlgEVCWedy1kBbHZBAwlpm6azdjFyMEhIqAt0f5R
	DMQUFnCUuHwgE6SCV8Be4tatJrBdnALBEl8nv4caeYxJ4t3Lq2AJfgF9iat/P0EdZC8x88oZ
	RohmQYkfk++xgNjMAloSm7c1sULY8hKb17xlnsAoMAtJ2SwkZbOQlC1gZF7FKJpamlxQnJSe
	a6RXnJhbXJqXrpecn7uJERKCX3cwLj1mdYhRgINRiYc30GNNoBBrYllxZe4hRgkOZiUR3m8b
	gUK8KYmVValF+fFFpTmpxYcYmTg4pRoY9zLqdTtfNbIO5bde53xmtdn6cwbBE13/5H5fqZdf
	dnDbTvU/U4JZjQ9kfxEuEjvtyGyZaJ177eMsg/xiS+2Gq6dknyu1FD1NlC0V+HF9o+jn6RbP
	m51/mMefS+cU9r95ca9w2MRX0Y9DmlY03zp7y/GVp93nFfqdN5XYb+Uyrj5obdz0a1GQEktx
	RqKhFnNRcSIArt+EMx8CAAA=

On Mon, 03 Jun 2013 08:05:22 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> > If you want to be able to enable or disable every pattern separetely, you
> > "setopt extendedglob kshglob noshglob" first.
> 
> Is the word "first" significant there?

No, they are completely separate controls.

It was just a bit of pedantry: until you did it, you weren't exerting
the level of control you (by hypothesis) wanted by using enable and
disable.

pws