From: Emanuel Berg <incal@dataswamp.org>
To: emacs-devel@gnu.org
Subject: Re: Emacs Lisp Linter fail to identify function defined in a "use-package" block
Date: Wed, 08 Nov 2023 09:56:16 +0100 [thread overview]
Message-ID: <87h6lwk4i7.fsf@dataswamp.org> (raw)
In-Reply-To: E1r0Yxe-00011V-SB@fencepost.gnu.org
Richard Stallman wrote:
> I thought that the need for a separate `lint' program was
> a design flaw, so instead of writing a free `lint' for GNU,
> I made GCC report those possible errors. Thus, the GNU
> system did not need a `lint' program. You only needed to run
> one program over your C source, that being GCC, and it would
> do both jobs. That proved to be a big improvement.
I agree it would be beneficial to have it all in one and only
one place.
In vanilla Emacs, warnings and suggestions are or can be
outputted from:
- checkdoc.el
- elint.el
- the byte compiler
- the native compiler
In MELPA there are:
- elisp-lint [1]
- package-lint [2]
elisp-lint has the advantage that it is a meta-linter of sort,
as it also outputs warnings from the byte compiler, from
checkdoc, and package-lint.
[1] https://github.com/gonewest818/elisp-lint/
[2] https://github.com/purcell/package-lint
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-11-08 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 0:32 Emacs Lisp Linter fail to identify function defined in a "use-package" block Kiong-Gē Liāu
2023-10-12 5:22 ` Emanuel Berg
2023-10-13 1:47 ` Emanuel Berg
2023-10-13 1:55 ` Emanuel Berg
2023-10-13 2:05 ` Emanuel Berg
2023-10-13 2:29 ` Emanuel Berg
2023-10-13 3:33 ` Emanuel Berg
2023-10-26 20:29 ` Emanuel Berg
2023-11-06 23:51 ` Emanuel Berg
2023-11-08 3:10 ` Richard Stallman
2023-11-08 8:56 ` Emanuel Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-11 17:19 Kiong-Gē Liāu
2023-10-10 14:51 Kiong-Gē Liāu
2023-10-10 22:25 ` Emanuel Berg
2023-10-11 0:59 ` Emanuel Berg
2023-10-11 1:43 ` Emanuel Berg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6lwk4i7.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.