GNU bug report logs - #37238
flymake feature request

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37238 in the body.
You can then email your comments to 37238 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: bruno cuconato <bcclaro <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: flymake feature request
Date: Fri, 30 Aug 2019 14:55:31 -0300

[Message part 1 (text/plain, inline)]

hi,

I wonder what your thoughts are on showing flymake diagnostics in the
minibuffer after a timeout, similarly to how flycheck does it, or how
https://github.com/akash-akya/emacs-flymake-cursor seems to do.

My thoughts are that this is not so simple* to implement as adding a
function to the overlay keymap (hence the existence of flymake-cursor)
and thus shouldn't be left to the user if it is deemed a worthy
feature; and that it would be nice to have as a built-in feature
instead of having it in a third party package since there are more
than two forks of flymake-cursor already and I'm happy to avoid MELPA.

Would you consider incorporating this functionality in flymake?

* there is a simple hack that seems to work though: enabling eldoc,
and using the `eldoc-documentation-function' to display the errors.

thank you,

-- bruno cuconato

[Message part 2 (text/html, inline)]

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: bruno cuconato <bcclaro <at> gmail.com>
Cc: 37238 <at> debbugs.gnu.org
Subject: Re: bug#37238: flymake feature request
Date: Fri, 20 May 2022 03:51:16 +0200

bruno cuconato <bcclaro <at> gmail.com> writes:

> I wonder what your thoughts are on showing flymake diagnostics in the
> minibuffer after a timeout, similarly to how flycheck does it, or how
> https://github.com/akash-akya/emacs-flymake-cursor seems to do.
>
> My thoughts are that this is not so simple* to implement as adding a
> function to the overlay keymap (hence the existence of flymake-cursor)
> and thus shouldn't be left to the user if it is deemed a worthy
> feature; and that it would be nice to have as a built-in feature
> instead of having it in a third party package since there are more
> than two forks of flymake-cursor already and I'm happy to avoid MELPA.
>
> Would you consider incorporating this functionality in flymake?

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

I tend to think that this sort of thing is best left to external
packages instead of having it in-core -- there's so many ways to display
stuff like this.

So I'm closing this bug report as a "wontfix".

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

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