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:48:29 +0200 Message-ID: <83k1i0n88i.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> <3D5EA6AB-F0DA-4B66-8592-A111C906B3AE@acm.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="72221"; mail-complaints-to="usenet@blaine.gmane.org" Cc: lokedhs@gmail.com, perry@piermont.com, philippe.vaucher@gmail.com, jaygkamat@gmail.com, acm@muc.de, emacs-devel@gnu.org To: Mattias =?utf-8?Q?Engdeg=C3=A5rd?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 15 20:48:43 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 1gujTX-000Ifo-3Y for ged-emacs-devel@m.gmane.org; Fri, 15 Feb 2019 20:48:43 +0100 Original-Received: from localhost ([127.0.0.1]:45342 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gujTW-0006S8-2l for ged-emacs-devel@m.gmane.org; Fri, 15 Feb 2019 14:48:42 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:37976) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gujTO-0006S1-3n for emacs-devel@gnu.org; Fri, 15 Feb 2019 14:48:35 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52250) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gujTM-0006t2-S4; Fri, 15 Feb 2019 14:48:33 -0500 Original-Received: from [176.228.60.248] (port=2011 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gujTM-0004JN-E8; Fri, 15 Feb 2019 14:48:32 -0500 In-reply-to: <3D5EA6AB-F0DA-4B66-8592-A111C906B3AE@acm.org> (message from Mattias =?utf-8?Q?Engdeg=C3=A5rd?= on Fri, 15 Feb 2019 19:43:15 +0100) 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:233395 Archived-At: > From: Mattias Engdegård > Date: Fri, 15 Feb 2019 19:43:15 +0100 > Cc: Alan Mackenzie , > Elias Mårtenson , > emacs-devel@gnu.org, philippe.vaucher@gmail.com, jaygkamat@gmail.com, > perry@piermont.com > > 15 feb. 2019 kl. 19.36 skrev Eli Zaretskii : > > > > 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? > > If I read the petitioners correctly, they want a global setting that > permits them to type a(b|c) instead of a\(b\|c\) in > isearch-forward-regexp and all other interactive commands. That is not going to happen any time soon, because it will break gobs of Emacs code. I don't see anyone proposing that, because they all understand the impossible implications.