From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-39415-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 9827 invoked by alias); 22 Sep 2016 16:48:41 -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: 39415
Received: (qmail 1315 invoked from network); 22 Sep 2016 16:48:41 -0000
X-Qmail-Scanner-Diagnostics: from mail-qt0-f171.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.216.171):SA:0(0.0/5.0):. 
 Processed in 0.318831 secs); 22 Sep 2016 16:48:41 -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,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.216.171 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=BHcFPO2w7iAGVBlKhjFwKOZgzAuZht8gyknLZL0scL4=;
        b=d5JkmCadIuCtAVSUSaPSqHobeLpma60YG1y9bQz8DxdIKSlelDJ6iYGhJSm0z/Knh4
         +ibaRhgNdwJMgyRrfvkiXQnzAr6v6NAqfr0gMi1KrKOZvFpnk8GHTj6GE7Tpf736ObmC
         YVR0eXgdf6qX3zAAL052fmuu0N6DnPxVsPOMb2DhIy7lbxm2eiTS2aI312HaB0bCjU61
         iq9wqPJJOhUqnqlF14QAQK9HPEtRfe8OQv8BK7f7lINSzjY088UNa5edmfJYuT9v0PjJ
         5rZyuGGBWlsegQHJNbgQFFMdSyP8V/XjTfwVTm7a+LrBNgfBROn7wI9HayvGZlX7pqhQ
         +Uiw==
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=BHcFPO2w7iAGVBlKhjFwKOZgzAuZht8gyknLZL0scL4=;
        b=a3bx6pX3uCxGWP39YCbREpp24QUwGRY/hMZ4nKG1AkoRvG9uZJE6A5alfpAD38nywW
         stNP5RJt9UsOba+FpI8In5EhfA6vAsiSQX10EEHIheMj3PWmHMuLixIXxsokHa8+mylA
         y9CV/dBLNXHWDXCHFQjQIKYDgpcUevXyaUk6vZ2kvWkNXWYHQb5p+BKRyLCbFToWwjJe
         16o4XeXUUdqxp3D2yhIbjakw+M2xDHOy7IyjELqO1GnLUrK1BlIefPXuKr05n+j9MWCF
         f9Fn1m1wESrCrKqMMSIIta+RqCkCIfuboj/rYiPADpYqv9TEtggqXkBnmKQk+nLlUBPZ
         Pxrg==
X-Gm-Message-State: AA6/9Rl3U4KdRl08sbbm/qTDpTiLZTYRMFv10sS8lL7DqtjcVV9hfN7nqtPu65CeiG+X4UBkhWgK9wFS7Cd1bw==
X-Received: by 10.200.51.54 with SMTP id t51mr2993362qta.110.1474562914391;
 Thu, 22 Sep 2016 09:48:34 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <160921141309.ZM3643@torch.brasslantern.com>
References: <CAKc7PVAdnzTRk8mUZVrFJHKWr_Q9-8whffw7DAUpnkYqwX24yg@mail.gmail.com>
 <CAKc7PVCjbaHiAm4ssJGtLLk-tN3o8SuN+wgzLUJUeeG2PFcVMA@mail.gmail.com>
 <CAKc7PVDT6D2_63z_eE2OKwusrwZknK7N6azCPhg_bu=5LxQC=w@mail.gmail.com>
 <CAKc7PVCxPM2OoLW6-FhF7nFO+qNTMCmiNo7xJbb=bDx6P66POg@mail.gmail.com>
 <CAKc7PVDfnz1Vm3=YzmZou5NG3YphyTwsA6-kWX=gHyknJdUJ9g@mail.gmail.com> <160921141309.ZM3643@torch.brasslantern.com>
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Thu, 22 Sep 2016 18:48:14 +0200
Message-ID: <CAKc7PVD6Aod7YmQYH9812C5KCBfrirFgRCwMF_iv4uKLZeo+1w@mail.gmail.com>
Subject: Re: [BUG] String equal when compared, processed differently via //
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8

On 21 September 2016 at 23:13, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Sep 21, 12:37pm, Sebastian Gniazdowski wrote:
> }
> } Ah no it doesn't help, it simply doesn't match at all and repeat output ...
>
> What specifically is wrong ("doesn't match at all") with the latter two?

I was referring to the mine (I:2:). It wasn't helping at all, just did
zero-match and repeated input, and terminal ate ^A, ^B, etc. so I
didn't notice.

Sorry for the mistake. Lost much time for this. Really glad there is
no such serious (@f) related bug. I've indeed put "}" in wrong place.

Thanks,
Sebastian Gniazdowski