From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-39219-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 15349 invoked by alias); 7 Sep 2016 10:39:32 -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: 39219
Received: (qmail 14609 invoked from network); 7 Sep 2016 10:39:32 -0000
X-Qmail-Scanner-Diagnostics: from mail-qk0-f178.google.com by f.primenet.com.au (envelope-from <sgniazdowski@gmail.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(209.85.220.178):SA:0(0.0/5.0):. 
 Processed in 0.329463 secs); 07 Sep 2016 10:39:32 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,
	SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1
X-Envelope-From: sgniazdowski@gmail.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.220.178 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc;
        bh=xPpUnQFuOINtTuGU7vFi8THVYBU4C+wNDLn51cQuMvE=;
        b=WC9tUm2CwoWvtfUAqCiSS+kvSg2DtklTaaciGLepXWwejhOjf0MNuzMW5r8Kky4apK
         ROIHlmxS/E6nhnjD25ELl1GGGwYUBViASTMdmKi+s+geVbZlU3wQQkdqPZy8KT+rvSXn
         l4EkBH7SdXuW3+cQXzxgmyzJMaqQMcgwrwcXvSF+em+bHfnTSfUDAR+kMqAdrsuRC9Fv
         aWxJNxqeI5f+1/bP6nZC2HeQy6x1S/19cAzzHDcdRG0x94dWtJzBYE8/lAB4x1OuZSbT
         xVwqveoAVzpUDnnXJD68RY8yfD//pxa51NVI4CvmPMioqPysMH5sXX8G5urwksKIywZ3
         MjQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc;
        bh=xPpUnQFuOINtTuGU7vFi8THVYBU4C+wNDLn51cQuMvE=;
        b=XBdM5CXHPttUl7kJltjPuXq3rA+F/PUftCflNLwVeCTmzwwk/h5cmE6DyhvO+bklEk
         vKEbWpNSv5a3HyTvz7RokIBuoJ9X0wGKXWBefaRMklA85FQzcLjogwsgKrUBE6bah1et
         QmNmVP3Cvq27TeW/DCjBu+0M6eAzeicMLaHYMUcltfdt8YI75Cxv5AXomgKgReG31p3L
         keh56f86H2d6XJjmO7SwIqRKjxLbmwtA3EAMIDpyNqBsHZn5cjH+cpx8/eLnPHOfri2e
         epbZ50Bw3+1ZncQYo9WilP+kmXhC6qjyHFjxpZ94GhN9sDsrbpHADaJbwQ3ewi5gcG4B
         9q+w==
X-Gm-Message-State: AE9vXwMjAS2Cp7PfUZ1DlCPCHOIEeXhVJ5AzBir7Z3//zajFW1nyuiDkIxmG94q0meQ/vkgKaRe93W/1NUr73Q==
X-Received: by 10.55.109.195 with SMTP id i186mr50279624qkc.3.1473244765997;
 Wed, 07 Sep 2016 03:39:25 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <160611101412.ZM12850@torch.brasslantern.com>
References: <CAKc7PVBSCgG4Y87L_PzCEWDk=-cQLFmLxwps_rfvUUuhA-Np+w@mail.gmail.com>
 <160611101412.ZM12850@torch.brasslantern.com>
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Wed, 7 Sep 2016 12:39:05 +0200
Message-ID: <CAKc7PVC93FCfC1Xn9keAEyBaiHfaV+_nbKSUzhmwKLmmm4soMg@mail.gmail.com>
Subject: Re: SH_GLOB influence on a script and on an autoload function
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: multipart/alternative; boundary=001a114873ccf1d040053be8869c

--001a114873ccf1d040053be8869c
Content-Type: text/plain; charset=UTF-8

On 11 June 2016 at 19:14, Bart Schaefer <schaefer@brasslantern.com> wrote:

> This is one of the drawbacks to attempting to accurately emulate parsing
> rules that are inherently contradictory.


It seems that pat="<full-featured zsh pattern here>" and then using
GLOB_SUBST via $~pat with SH_GLOB temporarily turned off should solve this?
But what about (N[1]) etc. modifiers... I'm thinking about a far away
possibility that one could fully work with emulate sh, having completions
not reporting errors.

Best regards,
Sebastian Gniazdowski

--001a114873ccf1d040053be8869c--