GNU bug report logs - #78459
flymake related locations (ancillary diagnostics)

Previous Next

Full log

Message #14 received at 78459 <at> debbugs.gnu.org (full text, mbox):

From: Mattias Engdegård <mattias.engdegard <at> gmail.com>
To: João Távora <joaotavora <at> gmail.com>
Cc: Spencer Baugh <sbaugh <at> janestreet.com>, 78459 <at> debbugs.gnu.org
Subject: Re: bug#78459: flymake related locations (ancillary diagnostics)
Date: Sat, 14 Jun 2025 21:19:15 +0200

20 maj 2025 kl. 21.24 skrev João Távora <joaotavora <at> gmail.com>:

> Similarly, you succinctly describe two cases, but what does "selecting a
> diagnostic" even mean?  I don't understand.

I didn't really have a specific method in mind. The user could do this actively, perhaps by clicking or pressing a key in the table of diagnostics or the code buffer. It could also be automatic, selecting the diagnostic when the user is lingering nearby.

One thing we can use that information for without user selection is keeping related locations and messages together in the table of diagnostics, so that sorting them by position doesn't result in a scrambled eggs list. This alone would be an improvement. Right now, there isn't even a way to convey the information to flymake.

Previous Next

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