From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27579 invoked from network); 16 Jun 2008 17:49:33 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.4 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 16 Jun 2008 17:49:33 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 61451 invoked from network); 16 Jun 2008 17:49:30 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 16 Jun 2008 17:49:30 -0000 Received: (qmail 4068 invoked by alias); 16 Jun 2008 17:49:26 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 25166 Received: (qmail 4058 invoked from network); 16 Jun 2008 17:49:25 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 16 Jun 2008 17:49:25 -0000 Received: from vms173001pub.verizon.net (vms173001pub.verizon.net [206.46.173.1]) by bifrost.dotsrc.org (Postfix) with ESMTP id A510C80525A4 for ; Mon, 16 Jun 2008 19:49:11 +0200 (CEST) Received: from torch.brasslantern.com ([71.121.0.2]) by vms173001.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K2K003GEHHVDVF6@vms173001.mailsrvcs.net> for zsh-workers@sunsite.dk; Mon, 16 Jun 2008 12:49:08 -0500 (CDT) Received: from torch.brasslantern.com (localhost.localdomain [127.0.0.1]) by torch.brasslantern.com (8.13.1/8.13.1) with ESMTP id m5GHn6RP009616 for ; Mon, 16 Jun 2008 10:49:07 -0700 Received: (from schaefer@localhost) by torch.brasslantern.com (8.13.1/8.13.1/Submit) id m5GHn6cI009615 for zsh-workers@sunsite.dk; Mon, 16 Jun 2008 10:49:06 -0700 Date: Mon, 16 Jun 2008 10:49:06 -0700 From: Bart Schaefer Subject: Re: PATCH: rewrite of completion matching In-reply-to: <200806161652.m5GGqnVh010847@pws-pc.ntlworld.com> To: zsh-workers@sunsite.dk (Zsh hackers list) Message-id: <080616104906.ZM9614@torch.brasslantern.com> MIME-version: 1.0 X-Mailer: OpenZMail Classic (0.9.2 24April2005) Content-type: text/plain; charset=us-ascii References: <200806161652.m5GGqnVh010847@pws-pc.ntlworld.com> Comments: In reply to Peter Stephenson "Re: PATCH: rewrite of completion matching" (Jun 16, 5:52pm) X-Virus-Scanned: ClamAV 0.92.1/7489/Mon Jun 16 16:51:24 2008 on bifrost X-Virus-Status: Clean On Jun 16, 5:52pm, Peter Stephenson wrote: } Subject: Re: PATCH: rewrite of completion matching } } Bart Schaefer wrote: } > OK, then what do each of the following mean, and how could I figure it } > out from the documentation? } } Well, by reading it, obviously. Touche. Skipping ahead, this is one bit that I wouldn't have understood from the documentation and that I'm not sure is correct: } m:{[:alnum:][:upper:]}={[:alnum:][:lower:]} } } is of very minor interest (match lower against upper provided some } alphanumeric, not specified but forced to be the same on both sides, } occurred in the previous character), and it's hard to think of good use } in practice. Really "occurred in the previous character"? If one had written m:{a-zA-Z0-9A-Z}={A-Za-z0-9a-z} That would not have implied two consecutive characters. The entire class on the left corresponds to the entire class on the right and is applied to each character independent of the ones around it. If what you said is true, you've introduced something completely new. So I'd have had the expectation that m:{[:alnum:][:upper:]}={[:alnum:][:lower:]} is at best a long way to write m:{[:upper:]}={[:lower:]} and at worst would be the same as m:{[:alnum:]}={[:alnum:]}. I'm going to have to reply to the rest of this later, out of time ...