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: Fri, 28 Feb 2020 23:40:05 +0200 Message-ID: <83zhd2e6h6.fsf@gnu.org> 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> <837e07gmka.fsf@gnu.org> <1c654ac9-10a2-4e5d-f77c-3b78bb580ffc@cs.ucla.edu> <83v9nqg8la.fsf@gnu.org> <298a093f-6eed-3a9f-99cf-bd17b9cb61f0@cs.ucla.edu> <83blpifp95.fsf@gnu.org> <81bfdae0-9fe1-f173-adb1-b5fe2ba2b808@cs.ucla.edu> <834kvafnwk.fsf@gnu.org> <8DA6D8F4-921B-4FB8-A7A3-CE75B10CE668@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="18181"; mail-complaints-to="usenet@ciao.gmane.io" Cc: cpitclaudel@gmail.com, eggert@cs.ucla.edu, emacs-devel@gnu.org To: Mattias =?utf-8?Q?Engdeg=C3=A5rd?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Feb 28 22:40:52 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 1j7nNM-0004df-7x for ged-emacs-devel@m.gmane-mx.org; Fri, 28 Feb 2020 22:40:52 +0100 Original-Received: from localhost ([::1]:54150 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j7nNL-0005Y8-9i for ged-emacs-devel@m.gmane-mx.org; Fri, 28 Feb 2020 16:40:51 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37474) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j7nMq-0004xY-Ok for emacs-devel@gnu.org; Fri, 28 Feb 2020 16:40:21 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48424) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1j7nMq-0002oo-EM; Fri, 28 Feb 2020 16:40:20 -0500 Original-Received: from [176.228.60.248] (port=3968 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1j7nMo-00027P-S9; Fri, 28 Feb 2020 16:40:20 -0500 In-reply-to: <8DA6D8F4-921B-4FB8-A7A3-CE75B10CE668@acm.org> (message from Mattias =?utf-8?Q?Engdeg=C3=A5rd?= on Fri, 28 Feb 2020 22:04:12 +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.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:245114 Archived-At: > From: Mattias Engdegård > Date: Fri, 28 Feb 2020 22:04:12 +0100 > Cc: Paul Eggert , cpitclaudel@gmail.com, > emacs-devel@gnu.org > > What about adding a variable controlling the change, defaulting to the stricter semantics? No, let's leave the default as it is now. Those who want such suspicious regular expressions flagged will customize the variable to a non-default value. Like they do with the warning options of a compiler.