From: Stefan Kangas <stefankangas@gmail.com>
To: 60040@debbugs.gnu.org
Cc: "João Távora" <joaotavora@gmail.com>
Subject: bug#60040: 29.0.50; flymake manual should document language support
Date: Tue, 13 Dec 2022 10:20:57 -0800 [thread overview]
Message-ID: <CADwFkm=Ga54ePMaq6Fbeom=wjsiEpRXWxtiPiwpftzpgWxQrwg@mail.gmail.com> (raw)
Severity: wishlist
Please consider adding a new chapter in (info "(flymake) Top") that
documents all built-in flymake support, and how to enable them
automatically.
I think such a chapter could also document the languages known to be
supported in packages on GNU ELPA and NonGNU ELPA.
It is currently hard to know which modes support flymake-mode, without
testing it in each mode. For example, I don't see that
`flymake-texinfo' or `perl-flymake' are currently documented anywhere
outside of their docstrings.
You can use `M-x apropos-function RET flymake RET', of course, but that
requires users to know implementation details of flymake (how to
implement a backend), as well as know that the functions must be loaded
(or autoloaded) for that to work, and finally you need to filter out a
lot of internal flymake implementation details and similar.
Note in particular that this is useful whether or not it is already
documented in the documentation for the respective packages (which it
most often is not, AFAICT).
See also:
https://www.flycheck.org/en/29/languages.html#flycheck-languages
next reply other threads:[~2022-12-13 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 18:20 Stefan Kangas [this message]
2022-12-13 18:28 ` bug#60040: 29.0.50; flymake manual should document language support João Távora
2023-09-10 19:11 ` Stefan Kangas
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='CADwFkm=Ga54ePMaq6Fbeom=wjsiEpRXWxtiPiwpftzpgWxQrwg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=60040@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).