From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "Perry E. Metzger" Newsgroups: gmane.emacs.devel Subject: Re: modern regexes in emacs Date: Fri, 15 Feb 2019 10:28:21 -0500 Message-ID: <20190215102821.162fe37a@jabberwock.cb.piermont.com> References: <20180616123704.7123f6d7@jabberwock.cb.piermont.com> <87po0qs6re.fsf@gmail.com> <83r2c9m8yj.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="55259"; mail-complaints-to="usenet@blaine.gmane.org" Cc: mattiase@acm.org, Philippe Vaucher , jaygkamat@gmail.com, lokedhs@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 15 16:29:25 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gufQb-000EDz-1m for ged-emacs-devel@m.gmane.org; Fri, 15 Feb 2019 16:29:25 +0100 Original-Received: from localhost ([127.0.0.1]:41588 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gufQa-0001Nn-17 for ged-emacs-devel@m.gmane.org; Fri, 15 Feb 2019 10:29:24 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:41304) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gufPk-0001NL-UY for emacs-devel@gnu.org; Fri, 15 Feb 2019 10:28:33 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gufPj-0008Sj-5L for emacs-devel@gnu.org; Fri, 15 Feb 2019 10:28:32 -0500 Original-Received: from hacklheber.piermont.com ([2001:470:30:84:e276:63ff:fe62:3400]:53410) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gufPe-0007kq-HA; Fri, 15 Feb 2019 10:28:27 -0500 Original-Received: from snark.cb.piermont.com (localhost [127.0.0.1]) by hacklheber.piermont.com (Postfix) with ESMTP id 1A72FD4; Fri, 15 Feb 2019 10:28:22 -0500 (EST) Original-Received: from jabberwock.cb.piermont.com (jabberwock.cb.piermont.com [10.160.2.107]) by snark.cb.piermont.com (Postfix) with ESMTP id EA5503C2001; Fri, 15 Feb 2019 10:28:21 -0500 (EST) In-Reply-To: <83r2c9m8yj.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2001:470:30:84:e276:63ff:fe62:3400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:233378 Archived-At: On Fri, 15 Feb 2019 16:18:12 +0200 Eli Zaretskii wrote: > > I think the purpose of this thread is to ask for emacs to support > > PCRE regexpes in commands like `query-replace-regexp`. > > > > Would this even be possible? I can imagine a whole lot of > > packages breaking if the regexp syntax changed, and changing it > > just for the user input in interactive functions looks a bit > > sketchy. > > It should be possible if we introduce new functions for PCRE, or if > we mark PCRE regexps in some special way, like put a special text > property on the string. I think the right thing is to introduce new functions for new-style regexps that parallel the old ones, and to allow users to bind things like the regexp flavors of isearch to the new-style versions if they wish. We can decide if we want the new-style versions to be the default search bindings at some distant date. One could also very slowly replace use of old-style regexp functions with the new-style regexp functions in lisp code, but that could be done over many many years if desired. Perry -- Perry E. Metzger perry@piermont.com