From: Stefan Kangas <stefankangas@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 60040-done@debbugs.gnu.org
Subject: bug#60040: 29.0.50; flymake manual should document language support
Date: Sun, 10 Sep 2023 12:11:55 -0700 [thread overview]
Message-ID: <CADwFkmm3j2dYENc1pB+DK=goofHHYDobz1v_CmoOwCU4VgUhfQ@mail.gmail.com> (raw)
In-Reply-To: <CALDnm50WuyMxuNddx0Qc-ch4yecyRZk_7jNRBYtT8eGJyYp5yw@mail.gmail.com> ("João Távora"'s message of "Tue, 13 Dec 2022 18:28:26 +0000")
João Távora <joaotavora@gmail.com> writes:
> Also, given the advent of LSP, I think the trend is
> for Flymake to be chiefly useful when connected
> with something like Eglot. Not exclusively so, but
> rather predominantly so.
I think you're completely right here, but this should be documented
prominently. So I've installed commit 9549612c53d on emacs-29.
Feel free to tweak, extend, rewrite, or improve it. It's very brief as
is, but I didn't know what more to say. Unfortunately, there's not much
need for a lot of documentation when things just work. ;-)
On a separate note, perhaps this note doesn't need to be on the first
page in Emacs 30.1:
Historically, Flymake used to accept diagnostics from a single
backend. Although obsolete, it is still functional. To learn how
to use and customize it, *note The legacy Proc backend::.
prev parent reply other threads:[~2023-09-10 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 18:20 bug#60040: 29.0.50; flymake manual should document language support Stefan Kangas
2022-12-13 18:28 ` João Távora
2023-09-10 19:11 ` Stefan Kangas [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='CADwFkmm3j2dYENc1pB+DK=goofHHYDobz1v_CmoOwCU4VgUhfQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=60040-done@debbugs.gnu.org \
--cc=joaotavora@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).