From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69120@debbugs.gnu.org
Subject: bug#69120: Spurious "function is not known to be defined" if defined in `use-package` body
Date: Wed, 14 Feb 2024 18:28:15 +0300 [thread overview]
Message-ID: <7aa4ac2b4eb557533d5b77b03b3ce2a74a674f21.camel@yandex.ru> (raw)
In-Reply-To: <86eddfxe7d.fsf@gnu.org>
On Wed, 2024-02-14 at 17:23 +0200, Eli Zaretskii wrote:
> > From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
> > Date: Wed, 14 Feb 2024 14:16:09 +0300
> >
> > I have many functions that are only useful inside a specific mode.
> > So I
> > group them with `use-package`, by defining them inside `:init` or
> > `:config` section, depending on the use.
> >
> > It turns out, byte-compiler does not consider such functions to be
> > defined and prints a warning about it.
> >
> > # Steps to reproduce (in terms of terminal commands)
> >
> > λ cat test.el
> > ;;; -*- lexical-binding: t -*-
> > (use-package prog-mode
> > :init
> > (defun hello()
> > (print "hello"))
> > (hello))
> > λ emacs -batch -f batch-byte-compile test.el
> >
> > In end of data:
> > test.el:6:4: Warning: the function ‘hello’ is not known to be
> > defined.
> >
> > ## Expected
> >
> > File gets compiled with no warnings
> >
> > ## Actual
> >
> > There's a warning
> >
> > test.el:6:4: Warning: the function ‘hello’ is not known to be
> > defined.
>
> What do you get if you macro-expand your code?
Wrapping the above code to a `(macroexpand …)` gives a:
"hello"
nil
next prev parent reply other threads:[~2024-02-14 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 11:16 bug#69120: Spurious "function is not known to be defined" if defined in `use-package` body Konstantin Kharlamov
2024-02-14 15:23 ` Eli Zaretskii
2024-02-14 15:28 ` Konstantin Kharlamov [this message]
2024-02-14 16:07 ` Eli Zaretskii
2024-02-14 16:10 ` Konstantin Kharlamov
2024-02-14 16:38 ` Eli Zaretskii
2024-02-14 16:58 ` Konstantin Kharlamov
2024-02-15 3:57 ` Konstantin Kharlamov
2024-02-15 4:00 ` Konstantin Kharlamov
2024-02-15 6:51 ` Eli Zaretskii
2024-02-15 15:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=7aa4ac2b4eb557533d5b77b03b3ce2a74a674f21.camel@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=69120@debbugs.gnu.org \
--cc=eliz@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.