From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?Mattias_Engdeg=C3=A5rd?= Newsgroups: gmane.emacs.devel Subject: Re: Errors indicated by ineffective backslashes in string literals Date: Sat, 16 Mar 2019 20:04:24 +0100 Message-ID: <1E86F07B-EE45-41EA-A081-00E9844BDE4C@acm.org> References: Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="86955"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Mar 16 20:05:12 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 1h5EcI-000MUS-Ta for ged-emacs-devel@m.gmane.org; Sat, 16 Mar 2019 20:05:11 +0100 Original-Received: from localhost ([127.0.0.1]:45190 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h5EcH-0005gH-Pa for ged-emacs-devel@m.gmane.org; Sat, 16 Mar 2019 15:05:09 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:53133) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h5Ebf-0005g5-RZ for emacs-devel@gnu.org; Sat, 16 Mar 2019 15:04:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h5Ebe-0008Ip-Ls for emacs-devel@gnu.org; Sat, 16 Mar 2019 15:04:31 -0400 Original-Received: from mail81c50.megamailservers.eu ([91.136.10.91]:45162 helo=mail18c50.megamailservers.eu) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h5Ebd-0008Hb-T6 for emacs-devel@gnu.org; Sat, 16 Mar 2019 15:04:30 -0400 X-Authenticated-User: mattiase@bredband.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=megamailservers.eu; s=maildub; t=1552763067; bh=SeZaXgTlcMsxe/4PiWjLW9miEiRp+m6yqZ5BHK6qDlg=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=oI1V/xFD20BcZ3yEXZdiApQump6c0mErYS20z7Kf79lHOYBX4OsqUaqXVNlRvh87S sz2BPtViOK6brpQhn3Pi/xrKA82op3JTRB35R785seANIFgTjT2gZBg1JsmEko5NFp dJlBnHJ5QxK+kIhddaMcS4hg0oqQ8iuD947aRRxE= Feedback-ID: mattiase@acm.or Original-Received: from [192.168.1.64] (c-e636e253.032-75-73746f71.bbcust.telenor.se [83.226.54.230]) (authenticated bits=0) by mail18c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id x2GJ4PC9001868; Sat, 16 Mar 2019 19:04:27 +0000 In-Reply-To: X-Mailer: Apple Mail (2.3445.102.3) X-CTCH-RefID: str=0001.0A0B0205.5C8D48BB.004F, 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=KOR08mNo c=1 sm=1 tr=0 a=M+GU/qJco4WXjv8D6jB2IA==:117 a=M+GU/qJco4WXjv8D6jB2IA==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=kj9zAlcOel0A:10 a=iRZporoAAAAA:8 a=9NpTxoGwTrNz7w-q6zAA:9 a=CjuIK1q_8ugA:10 a=NOBgFS-JBQ2l-kSd6-zu:22 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 91.136.10.91 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:234239 Archived-At: 16 mars 2019 kl. 19.25 skrev Stefan Monnier : >=20 >> Sorry to bother you again, but while trying to get a better = understanding of >> regexp usage and errors I found several ineffective backslashes in = string >> literals (like "\.") and decided to do something about them. >=20 > I went through something similar "recently" and added the = corresponding > highlighting in elisp-mode (see elisp--font-lock-backslash in = lisp-mode.el). Nice, thank you. I wrote a script to search for the help-echo property = to locate the errors. >> - (directory-files-recursively store-dir "\.gpg$")))) >> + (directory-files-recursively store-dir "\\.gpg$")))) > ^ > should be \\' >=20 > [ Yes, I know it's unrelated, but it's another common (minor) error. = ] Ah yes, sorry, should have done that while at it. Now I searched for = such cases and found lots, and decided to postpone it since it's mostly = cosmetic -- unless we are concerned about newlines in file names, which = we perhaps should be.