all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Kiong-Gē Liāu" <gongyi.liao@gmail.com>
To: incal@dataswamp.org, emacs-devel@gnu.org
Subject: Re: Emacs Lisp Linter fail to identify function defined in a "use-package" block
Date: Wed, 11 Oct 2023 12:19:50 -0500	[thread overview]
Message-ID: <4ff522f589b42363776b9bc66bb41d57845d49ec.camel@gmail.com> (raw)
In-Reply-To: 875y3e9kt8.fsf@dataswamp.org

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

Hi Emanuel,

I did some further tests and found that the "function *** is not known
to be defined" error only happen once for either a undefined function
or a function defined in a nested structure, as seen in the attached
screenshot.

1. The kkl0-fun, which is defined at top-level, linter shows no error
   at all about it
2. The kkl1-fun is defined as long as the *kk0l* global variable 
   is assigned as t
3. The first linter error appears when the kkl1-fun is called first
   time
4. At the second call-site of kkl1-fun, the linter "undefined-unction"
   error disappears 
5. the kkl2-fun is totally undefined, and linter identifies the
   undefined function error at its first call-site
6. at the second call-site of kkl2-fun, the undefined-function linter
   error disappears as well

So, it seems that elint starts to ignore undefined function starting
second call-site regardless that function is defined or not. we need
some further investigation on elint.el's elint-update-env function and
related functions.

Thanks,
Kiong-Gē.

[-- Attachment #2: Screenshot from 2023-10-11 08-56-48.png --]
[-- Type: image/png, Size: 49918 bytes --]

             reply	other threads:[~2023-10-11 17:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 17:19 Kiong-Gē Liāu [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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=4ff522f589b42363776b9bc66bb41d57845d49ec.camel@gmail.com \
    --to=gongyi.liao@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=incal@dataswamp.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.