From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29310 invoked by alias); 1 Apr 2017 10:22:06 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 22645 Received: (qmail 6575 invoked from network); 1 Apr 2017 10:22:06 -0000 X-Qmail-Scanner-Diagnostics: from aok120.rev.netart.pl 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(85.128.245.120):SA:0(0.0/5.0):. Processed in 2.173291 secs); 01 Apr 2017 10:22:06 -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=none autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: psprint@zdharma.org X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at zdharma.org does not designate permitted sender hosts) X-Virus-Scanned: by amavisd-new using ClamAV (19) Date: Sat, 1 Apr 2017 12:21:54 +0200 From: Sebastian Gniazdowski To: Bart Schaefer , zsh-users@zsh.org Message-ID: In-Reply-To: <170331141359.ZM24862@torch.brasslantern.com> References: <170330221929.ZM18456@torch.brasslantern.com> <170331141359.ZM24862@torch.brasslantern.com> Subject: Re: zregexparse X-Mailer: Airmail (231) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 31 march 2017 at 23:15:31, Bart Schaefer (schaefer=40brasslantern.com)= wrote: > =7D 1, 1, 1, 1, a > =7D 3, 3, 1, 2, bc > =20 > The return values from zregexparse are pretty strongly tailored to be > used with compset and compadd, and it does nothing useful with =24match= > and friends -- it's not tied into glob pattern referencing at all. > =20 > The values stored in =24p1 and =24p2 here are intended to calculate off= sets > into =22abc=22 for a call to compset -p, which isn't going to help you = with > ranges for highlighting. Also (though not significant in this eample), > zregexparse expects words joined with =24'=5C0'. Let me just express regret about this outcome. Redundancy is a cool thing= . I was able to filter =24history with (M)/:=23 and (R), and (R) turned o= ut to be faster. zregexparse could prove its value in e.g. static build w= ithout zsh/regex. One IRC user once reported problems with some completio= ns, because he sincerely configured BSD port as static build (no zsh/rege= x by default). I then quickly removed regex usage from =5Fhosts, but the = patch wasn't accepted, maybe because the problem wasn't highlighted (that= said, I may naively equate zsh/regex with zregexparse, but it's just tha= t shipping own regex engine is extreamly cool, at least for me). I once w= rote simple ANSI color codes parsing using (=23b), wonder if here the zre= gexparse could do something, but it would have to be able to progress acr= oss text, and lack of mend seems to be a problem. --=C2=A0 Sebastian Gniazdowski psprint /at/ zdharma.org