From: goncholden via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 54551@debbugs.gnu.org
Subject: bug#54551: show-paren-mode inconsistency
Date: Fri, 25 Mar 2022 04:20:39 +0000 [thread overview]
Message-ID: <0WZYJ8onIiWI4JsigrmlEGqkMLh1v1m8PYEhIC8hfU3s6tdWSPdE2eWEXWlzwwZ4UEkfEez_mlZTmfCy5akvKZTpu32mttK4b_qxu2VMIxs=@protonmail.com> (raw)
In-Reply-To: <02f5d0e52ab17015df7cffeda5600d17@webmail.orcon.net.nz>
------- Original Message -------
On Friday, March 25th, 2022 at 12:12 PM, Phil Sainty <psainty@orcon.net.nz> wrote:
> On 2022-03-25 11:48, goncholden wrote:
> > 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.
> That wouldn't make any sense for show-paren-mode.
> The cursor (point) is either between the ")" and " " characters, or
> else between the " " and "(" characters. Those are the only two
> possibilities, and in each case you would expect show-paren-mode to
> highlight the adjacent expression (to the left or to the right of the
> cursor, respectively).
I use the block colouring of the cursor, meaning that your valid description
in not so intuitive. Would it be possible to include a different interpretation
depending on the type of cursor display one is using?
> > But (setq show-paren-when-point-inside-paren t) does not do that.
> It's not documented as doing that, so there's not reason to expect
> that it might.
>
> I think you're looking for this library:
> https://www.emacswiki.org/emacs/HighlightSexp
Will try it out and report back about it.
next prev parent reply other threads:[~2022-03-25 4:20 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
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 [this message]
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='0WZYJ8onIiWI4JsigrmlEGqkMLh1v1m8PYEhIC8hfU3s6tdWSPdE2eWEXWlzwwZ4UEkfEez_mlZTmfCy5akvKZTpu32mttK4b_qxu2VMIxs=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=54551@debbugs.gnu.org \
--cc=goncholden@protonmail.com \
--cc=psainty@orcon.net.nz \
/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).