GNU bug report logs - #65035
29.1; Port flycheck-emacs-lisp-initialize-packages to flymake

Previous Next

Package: emacs;

Reported by: Antonio Romano <n58r <at> pm.me>

Date: Thu, 3 Aug 2023 10:05:01 UTC

Severity: normal

Found in version 29.1

To reply to this bug, email your comments to 65035 AT debbugs.gnu.org.

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

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#65035; Package emacs. (Thu, 03 Aug 2023 10:05:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Antonio Romano <n58r <at> pm.me>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Thu, 03 Aug 2023 10:05:02 GMT) Full text and rfc822 format available.

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

From: Antonio Romano <n58r <at> pm.me>
To: bug-gnu-emacs <at> gnu.org
Subject: 29.1; Port flycheck-emacs-lisp-initialize-packages to flymake
Date: Thu, 03 Aug 2023 10:04:24 +0000


Flycheck includes the "flycheck-emacs-lisp-initialize-packages"
customizable variable, which allows packages to be initialized in the
Emacs subprocess used to lint the elisp file. With this variable, it is
possible for the linter to be aware of autoloads from installed
packages.

I think that having such option on the built-in alternative "flymake"
would be a good quality-of-life addition, as this would make it more
suitable for linting personal configuration and only one M-x away from
any user who would want to try it.

Thanks in advance
This bug report was last modified 275 days ago.

Previous Next

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