From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Backslash-escaped brackets in string literals Date: Fri, 24 Jan 2020 12:36:52 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="120003"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Emacs developers To: Mattias =?windows-1252?Q?Engdeg=E5rd?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 24 18:37:44 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 1iv2tq-000V9B-Cs for ged-emacs-devel@m.gmane-mx.org; Fri, 24 Jan 2020 18:37:42 +0100 Original-Received: from localhost ([::1]:45810 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iv2tp-0002lw-Gr for ged-emacs-devel@m.gmane-mx.org; Fri, 24 Jan 2020 12:37:41 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56382) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iv2tA-0002Mv-Ck for emacs-devel@gnu.org; Fri, 24 Jan 2020 12:37:01 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iv2t8-0007aE-AL for emacs-devel@gnu.org; Fri, 24 Jan 2020 12:36:59 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:39770) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iv2t8-0007Zz-3Z for emacs-devel@gnu.org; Fri, 24 Jan 2020 12:36:58 -0500 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 0BC8F100791; Fri, 24 Jan 2020 12:36:57 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 35564100350; Fri, 24 Jan 2020 12:36:55 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1579887415; bh=WRYTZ08MTWQsLLLAcFWcpX5ZnWNoedTeNKMygnQBNyQ=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=PAwioItkdsqQwWMi0P8dnGYTgEOAD4JL8MUOd2LHzGHvN3Xcd5xDv1BJu6lmQ7l6/ OZsUzhu5XuMN54tst1szcvExRepdmtFnZGS5sl/OSnM67lPNBj9eRzg+8orOxMfU3p uXanKy9+DsMHkJphBPvDagAvoBYKUjLtQ7pwJTX8Mgi+ZGvUq328Oe1dKgIWJvN1me obzi0OuAxYlB+fOTUU/C3fMSSpi8WNGcKt0FRRaNhmSKSAq8VNgs6T+wyqjnS3UhJl 2gSGZ2mWVVV73H7HQA1erX+xrV1AR3PwF42yUMXzzGYFl5W/W+unNNokE1Xz/zDmka 4WT2OZDfQjXjQ== Original-Received: from alfajor (modemcable157.163-203-24.mc.videotron.ca [24.203.163.157]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id D4F8312095E; Fri, 24 Jan 2020 12:36:54 -0500 (EST) In-Reply-To: ("Mattias =?windows-1252?Q?Engdeg=E5rd=22's?= message of "Fri, 24 Jan 2020 16:12:51 +0100") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 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:244582 Archived-At: > First of all, is this still true? 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. > I rarely bother escaping brackets in doc strings and it doesn't seem > to cause any editing confusion. For example, beginning-of-defun > doesn't seem to be fooled by a '(' in column 1 inside a doc string. > (I do escape the (fn ...) annotation, probably out of superstition.) Indeed, it "should" work fine. You can report any misbehavior as a bug. > Moreover, these backslashes appear a bit everywhere (not just doc > strings), not only at bol, and not only before an opening bracket. Not my fault ;-) But yes, some authors probably decided it's easier to put them "everywhere" than to understand exactly when it's needed (and to fix the cases where refilling moves a `(` to/from BOL). > A list of all red backslashes attached. Without seeing the actual occurrences, it's hard to decide what to do with them. 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. Stefan