How to deal with 'function' not known to be defined

How to deal with 'function' not known to be defined

[Pankaj Jangid]

I have a lisp file `init-which-key.el` which is included in
`~/.emacs.d/init.el`.

#+BEGIN_SRC elisp
(require 'package)
(defun my/which-key-setup ()
  "Startup configuration for which-key."
  (unless (package-installed-p 'which-key)
    (package-install 'which-key))

  (which-key-mode 1))

(my/which-key-setup)
#+END_SRC

Flymake reports one warning - "The function 'which-key-mode" is not
known to be define.

I know that 'which-key-mode' is not available till the package is
installed. And flymake tries to compile and find errors and warnings.

What are the best practices to write such modular files that are free
from flymake warnings? Any pointers where I can read specifically on
this topic?

Re: How to deal with 'function' not known to be defined

[Emanuel Berg via Users list for the GNU Emacs text editor]

Pankaj Jangid wrote:

> I have a lisp file `init-which-key.el` which is
> included in `~/.emacs.d/init.el`.
>
> #+BEGIN_SRC elisp
> (require 'package)
> (defun my/which-key-setup ()
>   "Startup configuration for which-key."
>   (unless (package-installed-p 'which-key)
>     (package-install 'which-key))
>
>   (which-key-mode 1))
>
> (my/which-key-setup)
> #+END_SRC
>
> Flymake reports one warning - "The function
> 'which-key-mode" is not known to be define.
>
> I know that 'which-key-mode' is not available till
> the package is installed. And flymake tries to
> compile and find errors and warnings.
>
> What are the best practices to write such modular
> files that are free from flymake warnings?
> Any pointers where I can read specifically on
> this topic?

(require 'which-key)

?

-- 
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal

Re: How to deal with 'function' not known to be defined

[Stefan Monnier]

> I have a lisp file `init-which-key.el` which is included in
> `~/.emacs.d/init.el`.
[...]
> Flymake reports one warning - "The function 'which-key-mode" is not
> known to be define.

The linters activated in `emacs-lisp-mode` for `flymake` are inadequate
for the kind of code you find in `~/.emacs.d/init.el`.
They're designed for the kind of code you'd find in a package, like
those you can find in ELPA.

If you really want, you can try and write your `init.el` code in a way
that will silence those warnings, but it'll be inconvenient and the
benefits will be very slim and it could even be harmful (typically to
the startup time).

Making a linter that only emits those warnings when they're really
relevant in such a file will/would take a fair bit more effort.  In the
mean time I'd suggest you disable that linter in that file or ignore
those warnings.


        Stefan

Re: How to deal with 'function' not known to be defined

[Emanuel Berg via Users list for the GNU Emacs text editor]

Stefan Monnier wrote:

>> I have a lisp file `init-which-key.el` which is
>> included in `~/.emacs.d/init.el`.
>>
>> Flymake reports one warning - "The function
>> 'which-key-mode" is not known to be define.
>
> The linters activated in `emacs-lisp-mode` for
> `flymake` are inadequate for the kind of code you
> find in `~/.emacs.d/init.el`. They're designed for
> the kind of code you'd find in a package, like
> those you can find in ELPA.

I know only of the byte compiler, and `checkdoc', as
in

  (checkdoc-current-buffer t) ; TAKE-NOTES

This is a third way to analyze and improve
one's Lisp?

How does it work?

-- 
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal