all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Fri, 13 Oct 2023 05:33:19 +0200	[thread overview]
Message-ID: <87lec76vsw.fsf@dataswamp.org> (raw)
In-Reply-To: 87il7c8le4.fsf@dataswamp.org

I have now used elint on all my Elisp, totalling
196 files and 10 907 sloc.

The problems with elint, using `elint-current-buffer', are:

  - &rest arguments
  - `pcase'
  - `pcase-let'
  - lexical `let'-closures

The problems with vanilla Emacs source files, that are brought
to our attention thanks to elint, are:

  - they do not `provide' (e.g. startup.el)
  - they provide incorrectly (float-sup.el)
  - they don't use provide good enough (dired.el)

Of these problems, the byte-compiler, which is also a de facto
Elisp linter, only has the problem with lexical let-closures.
That particular problem can be remedied with
`declare-function' - but shouldn't have to be, and that method
doesn't work for elint.

The problem with vanilla Emacs sources files are not reported
by the byte-compiler.

-- 
underground experts united
https://dataswamp.org/~incal




  parent reply	other threads:[~2023-10-13  3:33 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 [this message]
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
  -- 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=87lec76vsw.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.