From: Fei <fei.yuanbw@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Drew Adams <drew.adams@oracle.com>
Cc: 13718@debbugs.gnu.org
Subject: bug#13718: [patch] prevents hl-line from overriding highlight-mode
Date: Fri, 15 Feb 2013 11:15:10 -0500 [thread overview]
Message-ID: <CAG8JBjCxxomDcZLRSfnazJ0NhwER4VhncSszBWjz5wboQB4VFA@mail.gmail.com> (raw)
In-Reply-To: <jwvmwv5zijb.fsf-monnier+emacs@gnu.org>
> hl-line seems to leave its overlay's priority unspecified (good!), which
> means that it should take precedence over overlays which are larger
> (e.g. span multiple lines) while smaller overlays within the current
> line should take precedence over it.
>
> Can you describe your particular case? What are the overlays that
> "disappear", what do they cover, and why do you think they should not
> "disappear" like that?
That's actually a reasonable alternative to my hard-coded solution,
but the problem is that it doesn't seem to work in every case: when I
open a file that has syntax highlighting (e.g. Bash or Python) and
then use highlight-phrase/regexp, the global-hl-line will have higher
priority than the highlight, no matter what the size of the highlight
is. If I do the same thing in text-mode, the problem does not occur.
(This was tested on 24.2.1-i386-mingw-nt6.1.7601 without any custom
configuration.)
> The priority here should be a user option, or at least a defvar that a user can
> tweak. Likewise, for other overlay priorities in Emacs.
That's fine too, as long as it can be changed without directly messing
with the internals. Currently there is no such variable available for
either hl-line or any of the highlights.
next prev parent reply other threads:[~2013-02-15 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 4:28 bug#13718: [patch] prevents hl-line from overriding highlight-mode Fei
2013-02-15 15:26 ` Drew Adams
2013-02-15 15:51 ` Stefan Monnier
2013-02-15 16:15 ` Fei [this message]
2013-02-15 17:30 ` Stefan Monnier
2013-02-15 17:49 ` Fei
2013-02-16 18:43 ` Fei
2013-02-16 18:56 ` Drew Adams
2013-02-15 17:45 ` Drew Adams
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=CAG8JBjCxxomDcZLRSfnazJ0NhwER4VhncSszBWjz5wboQB4VFA@mail.gmail.com \
--to=fei.yuanbw@gmail.com \
--cc=13718@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=monnier@iro.umontreal.ca \
/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).