From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: goncholden via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#54551: show-paren-mode inconsistency Date: Thu, 24 Mar 2022 22:48:35 +0000 Message-ID: References: <83ee2rccyk.fsf@gnu.org> Reply-To: goncholden Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21042"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 54551@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Mar 24 23:49:19 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1nXWGd-0005MS-0j for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 24 Mar 2022 23:49:19 +0100 Original-Received: from localhost ([::1]:37100 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nXWGa-0000Np-HB for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 24 Mar 2022 18:49:16 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:58872) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nXWGN-0000Nc-Nh for bug-gnu-emacs@gnu.org; Thu, 24 Mar 2022 18:49:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55721) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nXWGN-0002J7-8K for bug-gnu-emacs@gnu.org; Thu, 24 Mar 2022 18:49:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nXWGM-0001vo-Hv for bug-gnu-emacs@gnu.org; Thu, 24 Mar 2022 18:49:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: goncholden Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 24 Mar 2022 22:49:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 54551 X-GNU-PR-Package: emacs Original-Received: via spool by 54551-submit@debbugs.gnu.org id=B54551.16481621257399 (code B ref 54551); Thu, 24 Mar 2022 22:49:02 +0000 Original-Received: (at 54551) by debbugs.gnu.org; 24 Mar 2022 22:48:45 +0000 Original-Received: from localhost ([127.0.0.1]:49618 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nXWG5-0001vH-3j for submit@debbugs.gnu.org; Thu, 24 Mar 2022 18:48:45 -0400 Original-Received: from mail-4318.protonmail.ch ([185.70.43.18]:30417) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nXWG4-0001v4-1J for 54551@debbugs.gnu.org; Thu, 24 Mar 2022 18:48:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1648162117; bh=I5pB2Am78olOm1gF2ADDzfWVfr5Em9fBWJu+l26vz2o=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID; b=dK32LkHjxLVttECrciV0R7GmSbpxE4EBZJQDGKeGjkuNIjlnXzjhrB8XELBkZAbdA 09zM6RHd6jfS9UiEXG8n+3iJDBBu5CoX64sl+Rd9Q445DLHUi1ynMyElreM+esb4pN 83PuZokVB3EjXcsag3UThe+LF06JkYDQpZxv1HVT29OQ9k/ID3CzimYZYzZP32UTxY HT+7kxqjT/uKiPpF2z0neAc2/O3FjTM+a5wuuzYnEKJJgmwevixW4ne+4AxpY/GhHu fX1p5BVJeQnLKNjod0vYYfgbHj1vAhdU/bATuRdN5g2rS3sOKWgLQK5RJ4iF5GnG3A 2tWDbFnC+t8LA== In-Reply-To: <83ee2rccyk.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" X-ACL-Warn: , goncholden Xref: news.gmane.io gmane.emacs.bugs:228900 Archived-At: ------- Original Message ------- On Friday, March 25th, 2022 at 8:28 AM, Eli Zaretskii wrote: > > Date: Thu, 24 Mar 2022 20:13:55 +0000 > > > > From: goncholden via "Bug reports for GNU Emacs, > > > > the Swiss army knife of text editors" bug-gnu-emacs@gnu.org > > > > I am using show-paren-mode to highlight watching opening or closing par= entheses. > > > > Have seen that putting the cursor on the opening brace highlights the c= losing brace. But putting the cursor > > > > does not highlight the opening brace. One has to go to the character fo= llowing the closing brace. Because > > > > elisp customarily has many consecutive closing braces, using the consec= utive character to highlight the > > > > matching opening brace is counter productive. > > This is so typing the closing brace shows the matching opening brace. > > With your proposal, when I type the closing brace, the opening one > > will not be highlighted. > > So this is by design, and for a good reason. Thank you for the explanation. Consider the following command (setq initial-frame-alist '((width . 72) (height . 26)) ). Would be instructive that when one puts the cursor in the space between (wi= dth . 72) and (height . 26), the entire (width . 72) (height . 26) would be= highlighted. But (setq show-paren-when-point-inside-paren t) does not do that. Can be very non-intuitive when debugging. Also, if you put the cursor on t= he parenthesis following (height . 26), only (height . 26) gets highlighted= , rather than the entire (height . 26) (height . 26). Could some improvements be done about this?