unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Rudolf Adamkovič 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: 54634@debbugs.gnu.org
Subject: bug#54634: 29.0.50; Off-by-one highlighting
Date: Sat, 09 Apr 2022 22:41:09 +0200	[thread overview]
Message-ID: <m21qy6f0re.fsf@me.com> (raw)
In-Reply-To: <83pmlucw6y.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> If you can suggest a better setting for the priority/priorities of the
> two involved overlays, perhaps we could change the priority only when
> this style of show-paren-mode is used, and that would be an okay
> solution.

Eli, thank you for the reply!

In the reproduction case above, I would expect the active region highlight to
take precedence over the parenthesized expression highlight.  Effectively, the
active region highlight should cover the entire expression, including both of
its parentheses, rendering the expression highlight itself hidden.

I see two issues in play here:

(1) The priority, when using this particular style, does not make much sense.
For myself, I work around the issue as follows:

> Highlight parenthesized expressions with lower priority to avoid covering
> more important highlights, such as the active region highlight provided by
> the Transient Mark mode.
> 
> #+BEGIN_SRC emacs-lisp
> (setq show-paren-priority 0)
> #+END_SRC

(2) If we decide to fix the priority, then that uncovers the off-by-one active
region highlight bug that I reported.  I have waited for a couple of months
with reporting the bug to become sure that this configuration makes sense and
the highlight continues to confuse me.  It does and it does.

Rudy
-- 
"Be especially critical of any statement following the word
'obviously.'"
-- Anna Pell Wheeler, 1883-1966

Rudolf Adamkovič <salutis@me.com> [he/him]
Studenohorská 25
84103 Bratislava
Slovakia





      reply	other threads:[~2022-04-09 20:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30  6:36 bug#54634: 29.0.50; Off-by-one highlighting Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-30 11:36 ` Eli Zaretskii
2022-04-03 15:08   ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-03 15:43     ` Eli Zaretskii
2022-04-06  5:35       ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-06 11:01         ` Eli Zaretskii
2022-04-09 20:41           ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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=m21qy6f0re.fsf@me.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54634@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=salutis@me.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).