From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: :alnum: broken? Date: Wed, 26 Feb 2020 22:38:03 +0000 Message-ID: References: <86wo8flqct.fsf@stephe-leake.org> <86sgj3ljf0.fsf@stephe-leake.org> <5fecc0e1-1ee2-5a89-9297-b0b9aa4a8e9c@cs.ucla.edu> <03A37C4B-9FE8-4A25-9851-79BC8265455E@acm.org> <142e845d-eba3-5975-fa63-4c1b14ed4600@cs.ucla.edu> <3A14F30E-60EF-4C99-AC1A-9A1B2539169B@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="6879"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: K-9 Mail for Android To: emacs-devel@gnu.org, =?ISO-8859-1?Q?Mattias_Engdeg=E5rd?= , =?ISO-8859-1?Q?Cl=E9ment_Pit-Claudel?= , Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Feb 26 23:38:48 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j75KJ-0001hs-Te for ged-emacs-devel@m.gmane-mx.org; Wed, 26 Feb 2020 23:38:47 +0100 Original-Received: from localhost ([::1]:50972 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j75KI-0003TP-UB for ged-emacs-devel@m.gmane-mx.org; Wed, 26 Feb 2020 17:38:46 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34672) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j75Jm-00031u-Nu for emacs-devel@gnu.org; Wed, 26 Feb 2020 17:38:15 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52854) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1j75Jk-00077g-AH; Wed, 26 Feb 2020 17:38:12 -0500 Original-Received: from [109.253.200.137] (port=39481 helo=[10.130.151.118]) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1j75Jg-0007Gy-7O; Wed, 26 Feb 2020 17:38:11 -0500 In-Reply-To: <3A14F30E-60EF-4C99-AC1A-9A1B2539169B@acm.org> 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.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:245085 Archived-At: On February 26, 2020 10:01:24 PM GMT, "Mattias Engdeg=C3=A5rd" wrote: > 26 feb=2E 2020 kl=2E 22=2E24 skrev Cl=C3=A9ment Pit-Claudel > : >=20 > > I think your patch disallows thing like [:-:], which grep allows=2E >=20 > Very well, I've now made it more forgiving in this respect=2E Thank you! >=20 > Paul, I believe I misunderstood you at first; the change does not > check for POSIX equivalence classes or collation elements, on the > grounds that these are not accepted syntax in Emacs regexps anyway=2E If > you think it really is worth the trouble to add the analysis then say > so, but there is a smell of gold-plating (mixing metaphors) here=2E Please revert these changes=2E I already said that I wasn't interested in= making these regular expressions signal an error=2E If we want to flag these as potential mistakes, let's make the byte compi= ler warn about them, as Richard proposed=2E But I'm against making this a = run-time error=2E Thanks=2E