GNU bug report logs -
#34022
26.1; Region highlight has lower priority than flymake overlays
Previous Next
Reported by: Johann Klähn <johann <at> jklaehn.de>
Date: Wed, 9 Jan 2019 20:39:02 UTC
Severity: normal
Found in version 26.1
Fixed in version 27.1
Done: João Távora <joaotavora <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Johann Klähn <johann <at> jklaehn.de> writes:
> I just noticed a bug (?) that region becomes de-facto "invisible" due
> to its highlight overlay having a lower priority than the flymake
> overlays. This only happens when both region and flymake diagnostics
> are indicated using the same face property (background in my case). It
> becomes more apparent for larger flymake overlays.
>
> Steps to reproduce, starting from emacs -Q:
>
> • M-: (set-face-background flymake-note "yellow green")
You probably mean
(set-face-background 'flymake-note "yellow green")
> Flymake uses 100 as the offset to compute the default priority for its
> overlays:
> Is it intentional that 100 is used as the offset here? This has the
> effect that most priorities will be above that of the region overlay.
Yes, it was intentional. Doesn't mean that it's correct :-) Perhaps it
should be reduced to the 50's region and also use the (nil . <value>),
form which I didn't know about (so thanks for showing me this).
I don't know if there are any guide-lines for interoperation in this
front, so if someone more knowledgeable than me want to chime in...
Anyway, for now, you can probably work around this with
(push '(priority . (nil . 50)) (get :note 'flymake-overlay-control))
João
This bug report was last modified 5 years and 205 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.