unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: goncholden via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54551@debbugs.gnu.org
Subject: bug#54551: show-paren-mode inconsistency
Date: Thu, 24 Mar 2022 22:48:35 +0000	[thread overview]
Message-ID: <I01GRv-TGinyRLw0PZCrvlgqvy4nHAbbxxYsSn84ofNOarjEl7AD6Q8BjqBGfQfJ9HZksvOuyK_cCeR1MB2fgvH5jmhyjQoGaXPbn2v_7NI=@protonmail.com> (raw)
In-Reply-To: <83ee2rccyk.fsf@gnu.org>


------- Original Message -------

On Friday, March 25th, 2022 at 8:28 AM, Eli Zaretskii <eliz@gnu.org> 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 parentheses.
> >
> > Have seen that putting the cursor on the opening brace highlights the closing brace. But putting the cursor
> >
> > does not highlight the opening brace. One has to go to the character following the closing brace. Because
> >
> > elisp customarily has many consecutive closing braces, using the consecutive 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 (width . 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 the parenthesis following (height . 26), only (height . 26) gets highlighted, rather than the entire (height . 26) (height . 26).

Could some improvements be done about this?







  reply	other threads:[~2022-03-24 22:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 20:13 bug#54551: show-paren-mode inconsistency goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-24 20:28 ` Eli Zaretskii
2022-03-24 22:48   ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-03-25  0:12     ` Phil Sainty
2022-03-25  4:20       ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25  4:29         ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25  4:57         ` Phil Sainty
2022-03-25  5:23           ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25  5:53             ` Phil Sainty
2022-03-25  6:47     ` Eli Zaretskii
2022-03-25  7:10       ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25  7:21         ` Eli Zaretskii
2022-03-25  8:35           ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 10:15             ` Eli Zaretskii
2022-03-25  8:51         ` Stephen Berman
2022-03-25  9:32           ` Phil Sainty
2022-03-25 11:47           ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 11:56             ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 12:00               ` Stephen Berman
2022-03-24 21:34 ` Phil Sainty
2022-03-25 16:25   ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='I01GRv-TGinyRLw0PZCrvlgqvy4nHAbbxxYsSn84ofNOarjEl7AD6Q8BjqBGfQfJ9HZksvOuyK_cCeR1MB2fgvH5jmhyjQoGaXPbn2v_7NI=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54551@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=goncholden@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).