From: goncholden via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 54551@debbugs.gnu.org
Subject: bug#54551: show-paren-mode inconsistency
Date: Thu, 24 Mar 2022 20:13:55 +0000 [thread overview]
Message-ID: <lEUedyYWCSiSlVNmJyyvu8CNE5Ey993N9g9GdyrBzzrl_JH748GI7k5b6YL0EPFLhJ82DBh7THksjUbHqGuiZlYD0eB90sPLcoMK4VuK5Fo=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1088 bytes --]
next reply other threads:[~2022-03-24 20:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 20:13 goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-03-24 20:28 ` bug#54551: show-paren-mode inconsistency Eli Zaretskii
2022-03-24 22:48 ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='lEUedyYWCSiSlVNmJyyvu8CNE5Ey993N9g9GdyrBzzrl_JH748GI7k5b6YL0EPFLhJ82DBh7THksjUbHqGuiZlYD0eB90sPLcoMK4VuK5Fo=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=54551@debbugs.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).