unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: bruno cuconato <bcclaro@gmail.com>
Cc: 37238@debbugs.gnu.org
Subject: bug#37238: flymake feature request
Date: Fri, 20 May 2022 03:51:16 +0200	[thread overview]
Message-ID: <87wneh6kff.fsf@gnus.org> (raw)
In-Reply-To: <CAPWro-jEB-OMPHbL12WuQiGHxDq8gu5X6O2WxByf2WBn+fKiqA@mail.gmail.com> (bruno cuconato's message of "Fri, 30 Aug 2019 14:55:31 -0300")

bruno cuconato <bcclaro@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





      reply	other threads:[~2022-05-20  1:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30 17:55 bug#37238: flymake feature request bruno cuconato
2022-05-20  1:51 ` Lars Ingebrigtsen [this message]

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=87wneh6kff.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=37238@debbugs.gnu.org \
    --cc=bcclaro@gmail.com \
    /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).