From: "Kiong-Gē Liāu" <gongyi.liao@gmail.com>
To: emacs-devel@gnu.org
Subject: Emacs Lisp Linter fail to identify function defined in a "use-package" block
Date: Tue, 10 Oct 2023 09:51:27 -0500 [thread overview]
Message-ID: <14e940300c05e0f19efd14f10610192319372808.camel@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
Hi,
I found that the built-in Emacs lisp linter seems not able to
identify functions defined within a (even the same) use-package :config
block as the attached screenshot indicates: the "elisp-face-temp"
function is defined right above the "elisp-face" function, however, the
linter says that the "`elisp-face-temp' is not known to be defined".
Are there some further configurations required in order to make the
linter identifies functions defined in nested structure or we need to
change the linter's implementation code to make the linter to identify
functions those are not defined at top-level (i.e., defun block within
a use-package or with-eval-after-loan block)
Thanks,
Kiong-Gē.
[-- Attachment #2: Screenshot from 2023-10-10 09-37-53.png --]
[-- Type: image/png, Size: 284855 bytes --]
next reply other threads:[~2023-10-10 14:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 14:51 Kiong-Gē Liāu [this message]
2023-10-10 22:25 ` Emacs Lisp Linter fail to identify function defined in a "use-package" block Emanuel Berg
2023-10-11 0:59 ` Emanuel Berg
2023-10-11 1:43 ` Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2023-10-11 17:19 Kiong-Gē Liāu
2023-10-12 0:32 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
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=14e940300c05e0f19efd14f10610192319372808.camel@gmail.com \
--to=gongyi.liao@gmail.com \
--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.