From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11340 invoked by alias); 5 Mar 2017 19:00:00 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 40742 Received: (qmail 9395 invoked from network); 5 Mar 2017 19:00:00 -0000 X-Qmail-Scanner-Diagnostics: from know-smtprelay-omc-10.server.virginmedia.net by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(80.0.253.74):SA:0(-0.1/5.0):. Processed in 1.00684 secs); 05 Mar 2017 19:00:00 -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.1 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: p.w.stephenson@ntlworld.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _smtprelay.virginmedia.com designates 80.0.253.74 as permitted sender) X-Originating-IP: [82.132.227.196] X-Spam: 0 X-Authority: v=2.1 cv=WM+CJSYR c=1 sm=1 tr=0 a=iEafHRK3wv/+oQBts+7j9A==:117 a=iEafHRK3wv/+oQBts+7j9A==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=MWUjAzoEKyAA:10 a=q2GGsy2AAAAA:8 a=ZC_kVWi-vLIuPanXfX4A:9 a=QEXdDO2ut3YA:10 a=z9dJwno5l634igLiVhy-:22 Date: Sun, 05 Mar 2017 18:52:50 +0000 User-Agent: K-9 Mail for Android In-Reply-To: <170305104239.ZM25231@torch.brasslantern.com> References: <170304151137.ZM30694@torch.brasslantern.com> <170305080054.ZM24832@torch.brasslantern.com> <20170305161720.6f3773d6@ntlworld.com> <170305104239.ZM25231@torch.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [BUG] SIGSEGV under certain circumstances To: zsh-workers@zsh.org From: Peter Stephenson Message-ID: <5096E600-D76C-4F71-BE93-C46F256BA7D7@ntlworld.com> On 5 March 2017 18:42:39 GMT+00:00, Bart Schaefer wrote: >On Mar 5, 4:17pm, Peter Stephenson wrote: >} >} The matcher code doesn't handle non-ASCII characters, and probably >never >} wlll --- I spent ages looking at this some years ago until I realised >I >} was getting nowhere=2E > >Maybe there's a way to have cfp_matcher_pats() bail out with failure as >soon as it encounters any non-ascii character? It needs at least to be able to do trivial matching, character for character, or it becomes unusable=2E pws --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E