GNU bug report logs - #66041
30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?

Previous Next

Full log

View this message in rfc822 format

From: Jim Porter <jporterbugs <at> gmail.com>
To: João Távora <joaotavora <at> gmail.com>, Eli Zaretskii <eliz <at> gnu.org>
Cc: 66041 <at> debbugs.gnu.org
Subject: bug#66041: 30.0.50; Should 'flymake-note-echo' inherit from 'compilation-info'?
Date: Mon, 18 Sep 2023 10:44:51 -0700

On 9/18/2023 5:52 AM, João Távora wrote:
> Yes, something like that.  Skimming the code, I think I meant for only
> one overlay, not two, to be the end-of-line overlay containing the two
> strings.  But this was tricky to implement and I probably missed an
> edge case.  There is a FIXME there, have to investigate.
> 
> Anyway, since I have your interest, any suggestions on how you would
> implement this? Knowing that this feature is upposed to display
> multiple pieces of relatively short cursor-unreachable text visually
> after the end -of-line (the text being the diagnostic text, naturally).

For what it's worth, I think it would be nice to have a single overlay, 
showing only the highest-severity message, and if there are more, add a 
"(+ N more)" suffix. Then, assuming it's possible to implement, you 
could click/hover over it to get a popup of some sort with all the 
messages. That way you can't overload the UI with many messages (which 
in practice might all be from the same underlying problem in your code).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.