From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-31449-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 5045 invoked by alias); 3 Jun 2013 15:05:43 -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: 31449
Received: (qmail 7226 invoked from network); 3 Jun 2013 15:05:29 -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=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,
	RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2
Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:x-gm-message-state;
        bh=/zr+6/xIG40H9bOqgtkuBLqa3yr1vjhvWDAT8BGZqrY=;
        b=YTA1hEZbqBlToqMfAPZaag+9idAahqsF0igh/QQPlU4aaavzOvEjHobkTe7te9nxLh
         weBJMvlJjFF6WRvuQzjCbAu4k+32uhZaNWQUxzGjCCuLsucroifxTaKwQw/fyLmXdera
         1y9oNX6hMvWXehZsjgMzuaVDKVp2UzsfAiq0FwhUrqjJjzt6ONr5gMG0E2S8q1KnlEP2
         ShnV1/RX1OhdGp/fTqIC9ZnXht8zDpDmC1foytRJIYLIhFEAVqahAKJMwqp6xI5sVjBL
         0AmUPDG//puBra7tIQxiPwaQ7ZB5I3IGABAEL2BOW/S8GFVvd5xuNP8nc5iV0lgwL4P1
         /Ocg==
MIME-Version: 1.0
X-Received: by 10.66.162.67 with SMTP id xy3mr24472964pab.94.1370271922594;
 Mon, 03 Jun 2013 08:05:22 -0700 (PDT)
In-Reply-To: <20130603094014.4728e466@pwslap01u.europe.root.pri>
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>
Date: Mon, 3 Jun 2013 08:05:22 -0700
Message-ID: <CAH+w=7advMYcjCGL1yvZN2BvBV1iN20Nnm0jsoQ+UXQuJ1RiOg@mail.gmail.com>
Subject: Re: PATCH: configurability of pattern characters, part 1
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Content-Type: multipart/alternative; boundary=047d7b86e3e4313a7d04de414b56
X-Gm-Message-State: ALoCoQllqc7ji3dlgJuq5r9EmdLSo1U4jonoUr+OBX/Q08l6iXWk6cB4KC32MkkOMdksuDNVFoiy

--047d7b86e3e4313a7d04de414b56
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jun 3, 2013 at 1:40 AM, Peter Stephenson
<p.stephenson@samsung.com>wrote:

> On Sun, 02 Jun 2013 00:16:27 -0700
> Bart Schaefer <schaefer@brasslantern.com> wrote:
> > % setopt kshglob
> > % disable -p '+('
> > % setopt kshglob
> >
> > Does the setopt re-enable '+(' or does it remain disabled?
>
> It remains disabled: that's a separate set of controls.


OK, so one way to think about this is that "disable" controls whether the
syntax is available, and setopt controls whether the syntax is used.
 Earlier, though, you said:

> 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?  E.g., does that mean that if I do

% unsetopt kshglob
% disable -p '+('
% setopt kshglob

that '+(' will be enabled?  (I know, I could apply the patch and try it,
but I'm interested in the intentions behind it.)

--047d7b86e3e4313a7d04de414b56--