From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34022@debbugs.gnu.org, "Johann Klähn" <johann@jklaehn.de>
Subject: bug#34022: 26.1; Region highlight has lower priority than flymake overlays
Date: Fri, 11 Jan 2019 09:33:33 +0000 [thread overview]
Message-ID: <877efbmtci.fsf@gmail.com> (raw)
In-Reply-To: <83o98nhcst.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Jan 2019 09:29:54 +0200")
[BTW Johann: to CC the bug tracker, use 34022@debbugs.gnu.org, not
bug-gnu-emacs@gnu.org, since this will create a new bug, and has the
potential to annoy maintainers :-). I'm guilty of that too, since I
replied to all in the email you did that (and so created another bug).]
Eli Zaretskii <eliz@gnu.org> writes:
> I'm not sure what I'm supposed to chime in about. Are you asking
> whether it's okay for Flymake to use the same technique as the
> region's overlay?
I guess he is, yes. It's a problem I didn't encounter during
development because the face properties of the Flymake overlays and the
region don't clash when using the default settings.
> Or are you asking something else? If the former,
> I'm not sure I understand the problem well enough to answer the
> question.
In Flymake multiple overlays (error, warning, note) can overlap and
priorities are used so that an error is never hidden by a note. I based
thosed priorities in the 100's range (so note = 101, warning=102,
error=103, sth like that). 100 was a number chosen quite arbitrarily
which worked fine until Johann noticed the bug (I do think it's a bug).
>In particular, how is Flymake different from any other package which
>uses overlays to mark portions of text?
Perhaps it isn't. Can you point me to other packages that leave
persistent region-resisting overlays in the buffer? (or that "play nice"
with the region, for some meaning of "nice").
João
next prev parent reply other threads:[~2019-01-11 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 20:33 bug#34022: 26.1; Region highlight has lower priority than flymake overlays Johann Klähn
2019-01-09 20:52 ` João Távora
2019-01-10 21:06 ` Johann Klähn
2019-01-10 22:03 ` João Távora
[not found] ` <1547153959.1638293.1631244736.794AFB75@webmail.messagingengine.com>
[not found] ` <83o98nhcst.fsf@gnu.org>
2019-01-11 9:33 ` João Távora [this message]
2019-01-11 19:14 ` Eli Zaretskii
2019-01-11 20:04 ` João Távora
2019-01-11 21:00 ` Eli Zaretskii
2019-11-02 16:17 ` João Távora
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=877efbmtci.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=34022@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=johann@jklaehn.de \
/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).