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: Backslash-escaped brackets in string literals Date: Fri, 24 Jan 2020 23:22:54 +0100 Message-ID: <64ECD2AB-962B-4781-BFBA-6357277C9599@acm.org> References: Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="11628"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Emacs developers To: Stefan Monnier , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 24 23:23:47 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 1iv7Mh-0002yQ-4q for ged-emacs-devel@m.gmane-mx.org; Fri, 24 Jan 2020 23:23:47 +0100 Original-Received: from localhost ([::1]:48716 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iv7Mg-00043D-8P for ged-emacs-devel@m.gmane-mx.org; Fri, 24 Jan 2020 17:23:46 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37621) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iv7Ly-0003Kp-Fm for emacs-devel@gnu.org; Fri, 24 Jan 2020 17:23:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iv7Lx-00039v-9E for emacs-devel@gnu.org; Fri, 24 Jan 2020 17:23:02 -0500 Original-Received: from mail213c50.megamailservers.eu ([91.136.10.223]:34914 helo=mail194c50.megamailservers.eu) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iv7Lv-00037U-Vw; Fri, 24 Jan 2020 17:23:01 -0500 X-Authenticated-User: mattiase@bredband.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=megamailservers.eu; s=maildub; t=1579904577; bh=6Dub9DBhgZLmJORWrpIPg5CsCiOzWa0/ZSrrKMsnqqY=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=KHC5VK3yE63nQP6J6oe9512CEUKgsCyz4CFQAwV28/wsVYbnGu7b8kjHk+S4F2K+W LzQ1WNcAagmRus65xv4RT5T9dys/AwDkhrsubByT9b/DSTNwZbj0LgJZClyXmrwY56 mwqPUxEyxPSzHYMpR9TmKyB9AL6bJ4aoCmCDsc+4= Feedback-ID: mattiase@acm.or Original-Received: from [192.168.0.4] (c188-150-171-71.bredband.comhem.se [188.150.171.71]) (authenticated bits=0) by mail194c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id 00OMMtAH009518; Fri, 24 Jan 2020 22:22:57 +0000 In-Reply-To: X-Mailer: Apple Mail (2.3445.104.11) X-CTCH-RefID: str=0001.0A0B0214.5E2B6E41.0033, 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=A9kSwJeG c=1 sm=1 tr=0 a=SF+I6pRkHZhrawxbOkkvaA==:117 a=SF+I6pRkHZhrawxbOkkvaA==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=kj9zAlcOel0A:10 a=M51BFTxLslgA:10 a=iRZporoAAAAA:8 a=xFhbfwGFxDGdp28aTxMA: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.223 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:244590 Archived-At: Eli and Stefan, thanks for explaining. 24 jan. 2020 kl. 18.36 skrev Stefan Monnier : > Yes and no. We have started to remove dependence on this, but there's > still some ways to go. Eli mentioned `C-x 4 a` but there are others. Actually, I tried to provoke C-x 4 a into a fit but failed. Perhaps I = just didn't have enough patience. > Those that occur within "normal strings" would benefit from > being fixed (i.e. removing the backslash). Those that apply to > something else than an open paren probably should be fixed as well. What I've done now is to remove (or, in some cases, double) redundant = backslashes except \( in doc strings. We probably could do away with = more of them, but I tweaked the tool to ignore the rest so it's good = enough for now.