From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: modern regexes in emacs Date: Fri, 15 Feb 2019 21:52:04 +0200 Message-ID: <83imxkn82j.fsf@gnu.org> References: <20180616123704.7123f6d7@jabberwock.cb.piermont.com> <87po0qs6re.fsf@gmail.com> <83r2c9m8yj.fsf@gnu.org> <17581DA9-7DCA-432E-A2E8-E5184DFA8B4B@acm.org> <20190215114728.0785e891@jabberwock.cb.piermont.com> <20190215175405.GA5438@ACM> <83lg2gnbky.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="91383"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 15 20:52:21 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 1gujX3-000Nfp-Fa for ged-emacs-devel@m.gmane.org; Fri, 15 Feb 2019 20:52:21 +0100 Original-Received: from localhost ([127.0.0.1]:45384 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gujX2-0007F1-EZ for ged-emacs-devel@m.gmane.org; Fri, 15 Feb 2019 14:52:20 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:38565) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gujWr-0007Er-EU for emacs-devel@gnu.org; Fri, 15 Feb 2019 14:52:12 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52314) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gujWp-0004e2-TW; Fri, 15 Feb 2019 14:52:09 -0500 Original-Received: from [176.228.60.248] (port=2236 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gujWo-0004ag-Ls; Fri, 15 Feb 2019 14:52:07 -0500 In-reply-to: (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Fri, 15 Feb 2019 13:46:23 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:233396 Archived-At: > From: Clément Pit-Claudel > Date: Fri, 15 Feb 2019 13:46:23 -0500 > > On 15/02/2019 13.36, Eli Zaretskii wrote: > > I proposed to have a separate set of functions that will accept PCRE > > syntax. That would allow everyone to have what they want: you to use > > the "classic" regexps, and those who want PCRE to have that. Where's > > the problem with that? > > I think that solution doesn't let you pass regexps using fancy PCRE features to existing code through defvars and defcustoms. As a concrete example, sometimes assertions would be useful in regexps that define outlines, or in syntax highlighting, or in comment marker definitions. Then those who want that will need to come up with either a function that converts PCRE to the traditional syntax, or invent new functions for outlines, syntax highlighting, etc. for that. You cannot seriously propose a global setting that will switch to PCRE syntax, as that will cause a lot of breakage. The original motivation was to provide PCRE in _commands_. Suddenly we are talking about using PCRE everywhere? Please hold your horses.