From: Phil Sainty <psainty@orcon.net.nz>
To: goncholden <goncholden@protonmail.com>
Cc: 54551@debbugs.gnu.org
Subject: bug#54551: show-paren-mode inconsistency
Date: Fri, 25 Mar 2022 17:57:45 +1300 [thread overview]
Message-ID: <5b634871f981330f5d47a53aff2a318d@webmail.orcon.net.nz> (raw)
In-Reply-To: <0WZYJ8onIiWI4JsigrmlEGqkMLh1v1m8PYEhIC8hfU3s6tdWSPdE2eWEXWlzwwZ4UEkfEez_mlZTmfCy5akvKZTpu32mttK4b_qxu2VMIxs=@protonmail.com>
On 2022-03-25 17:20, goncholden wrote:
> 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?
The position at point is the same no matter what the cursor
looks like, and the behaviour is based on where point is, so
for the current code the appearance of the cursor is irrelevant.
You *could* make the code test the cursor type and change its
behaviour in accordance with what it thought the cursor looked
like, but I'd really recommend just getting familiar with the
existing (and very consistent) behaviour, and remembering what
it is that the cursor actually represents.
> > I think you're looking for this library:
> > https://www.emacswiki.org/emacs/HighlightSexp
>
> Is HighlightSexp only relevant for use with lisp-mode-hook
> and emacs-lisp-mode-hook ?
Anything lisp-based should certainly work, but it's more generic
than that. Not every major mode would be relevant, but you can
experiment with different modes and see whether it works.
-Phil
next prev parent reply other threads:[~2022-03-25 4:57 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
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 [this message]
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=5b634871f981330f5d47a53aff2a318d@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--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).