From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?utf-8?Q?Mattias_Engdeg=C3=A5rd?= Newsgroups: gmane.emacs.devel Subject: Re: :alnum: broken? Date: Sun, 23 Feb 2020 11:21:58 +0100 Message-ID: References: <86wo8flqct.fsf@stephe-leake.org> <86sgj3ljf0.fsf@stephe-leake.org> <5fecc0e1-1ee2-5a89-9297-b0b9aa4a8e9c@cs.ucla.edu> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) 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="43099"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stephen Leake , emacs-devel To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Feb 23 11:23:06 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 1j5oPg-000B69-HA for ged-emacs-devel@m.gmane-mx.org; Sun, 23 Feb 2020 11:23:04 +0100 Original-Received: from localhost ([::1]:51398 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j5oPf-0003L9-Fz for ged-emacs-devel@m.gmane-mx.org; Sun, 23 Feb 2020 05:23:03 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54447) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j5oOx-0002oR-FU for emacs-devel@gnu.org; Sun, 23 Feb 2020 05:22:20 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j5oOw-0005eX-23 for emacs-devel@gnu.org; Sun, 23 Feb 2020 05:22:19 -0500 Original-Received: from mail151c50.megamailservers.eu ([91.136.10.161]:48564 helo=mail50c50.megamailservers.eu) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1j5oOv-0005dj-Fw for emacs-devel@gnu.org; Sun, 23 Feb 2020 05:22:18 -0500 X-Authenticated-User: mattiase@bredband.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=megamailservers.eu; s=maildub; t=1582453322; bh=3bWdjTFsilVZUISpOBcfsndyOYRzE5mTWjppTvWHHs0=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=JzEvTg6NqjgUVrsKY/IO/QDGMnHv5QTLuwrsUHwlVWfNamu1MLpSMXVX/b9HCu07b 8psYjOSRiZXrTPennhX5D8KmIJLHLUGRdGpJXkd4/XvyJC2eNtGLh0uaY3RoO3q8Hc J/dwQIw28HQiK0PdxDBQaQ4v/I829u3wIV5+vTxU= Feedback-ID: mattiase@acm.or Original-Received: from stanniol.lan (c-6f4fe655.032-75-73746f71.bbcust.telenor.se [85.230.79.111]) (authenticated bits=0) by mail50c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id 01NALwFt023506; Sun, 23 Feb 2020 10:22:01 +0000 In-Reply-To: <5fecc0e1-1ee2-5a89-9297-b0b9aa4a8e9c@cs.ucla.edu> X-Mailer: Apple Mail (2.3445.104.11) X-CTCH-RefID: str=0001.0A0B0203.5E52524A.002F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.3 cv=N4FX6F1B c=1 sm=1 tr=0 a=fHaj9vQUQVKQ4sUldAaXuQ==:117 a=fHaj9vQUQVKQ4sUldAaXuQ==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10 a=M51BFTxLslgA:10 a=kf0JAXOGuRu17sqVywwA:9 a=QEXdDO2ut3YA:10 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 91.136.10.161 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:245039 Archived-At: 22 feb. 2020 kl. 02.09 skrev Paul Eggert : > That is, GNU grep treats a bracket expression like '[:space:]' as an = error, since it's inevitably a typo. (POSIX does not allow this behavior = so the diagnostic is suppressed if POSIXLY_CORRECT is set.) Such a check is obviously unsound, strictly speaking, which may be a = reason for objecting to it. But in practice? It would have to be na=C3=AFv= e regexp-building code that puts characters inside square brackets = without eliminating duplicates, like (defun make-char-regexp (char-list) (concat "[" (apply #'string char-list) "]")) and given our experience in regexp mistakes, such code probably exists = in use somewhere. I'm still in favour of the check since it would be = cheap and helpful, and false positives unlikely. It is a fairly = infrequent blunder, though.