About the usage of `with-eval-after-load'.

About the usage of `with-eval-after-load'.

[Hongyi Zhao]

`C-h o with-eval-after-load RET' gives the following description:

with-eval-after-load is a Lisp macro in ‘subr.el’.

(with-eval-after-load FILE &rest BODY)

Execute BODY after FILE is loaded.
FILE is normally a feature name, but it can also be a file name,
in case that file does not provide any feature.  See ‘eval-after-load’
for more details about the different forms of FILE and their semantics.
;;;

Based on the above explanation, it seems that only one FILE can be
used, but according to my tries, the following code snippet also take
effect:

  (add-hook 'python-mode-hook 'hs-minor-mode)
  (with-eval-after-load
    "python"
    (progn
      (define-key python-mode-map (kbd "C-c TAB") 'hs-toggle-hiding)
      (add-to-list
'python-shell-completion-native-disabled-interpreters "jupyter")
      )

    'elpy (pyvenv-activate "~/.pyenv/versions/datasci")
    )

Is there anything wrong with my understanding of this macro? Any hints
will be helpful.

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: About the usage of `with-eval-after-load'.

[Omar Polo]

h
Hongyi Zhao <hongyi.zhao@gmail.com> writes:

> `C-h o with-eval-after-load RET' gives the following description:
>
> with-eval-after-load is a Lisp macro in ‘subr.el’.
>
> (with-eval-after-load FILE &rest BODY)
>
> Execute BODY after FILE is loaded.
> FILE is normally a feature name, but it can also be a file name,
> in case that file does not provide any feature.  See ‘eval-after-load’
> for more details about the different forms of FILE and their semantics.
> ;;;
>
> Based on the above explanation, it seems that only one FILE can be
> used, but according to my tries, the following code snippet also take
> effect:
>
>   (add-hook 'python-mode-hook 'hs-minor-mode)
>   (with-eval-after-load
>     "python"
>     (progn
>       (define-key python-mode-map (kbd "C-c TAB") 'hs-toggle-hiding)
>       (add-to-list
> 'python-shell-completion-native-disabled-interpreters "jupyter")
>       )
>
>     'elpy (pyvenv-activate "~/.pyenv/versions/datasci")
>     )

this is wrong.  as the signature says, it accepts a first argument
"file" and then the body to execute.  here, it seems that you want to
execute something when `python' is loaded and something else when `elpy'
is loaded, which warrants two `with-eval-after-load':

(with-eval-after-load 'python
  (define-key ...)
  (add-to-list ...))

(with-eval-after-load 'elpy
  (pyvenv-activate ...))

Other than that, I don't usually write python so can't comment further
on the code

> Is there anything wrong with my understanding of this macro? Any hints
> will be helpful.
>
> Regards

Cheers,

Re: About the usage of `with-eval-after-load'.

[Joost Kremers]

On Sat, Sep 18 2021, Hongyi Zhao wrote:
> `C-h o with-eval-after-load RET' gives the following description:
>
> with-eval-after-load is a Lisp macro in ‘subr.el’.
>
> (with-eval-after-load FILE &rest BODY)
>
> Execute BODY after FILE is loaded.
> FILE is normally a feature name, but it can also be a file name,
> in case that file does not provide any feature.  See ‘eval-after-load’
> for more details about the different forms of FILE and their semantics.
> ;;;
>
> Based on the above explanation, it seems that only one FILE can be
> used, but according to my tries, the following code snippet also take
> effect:
>
>   (add-hook 'python-mode-hook 'hs-minor-mode)
>   (with-eval-after-load
>     "python"
>     (progn
>       (define-key python-mode-map (kbd "C-c TAB") 'hs-toggle-hiding)
>       (add-to-list
> 'python-shell-completion-native-disabled-interpreters "jupyter")
>       )
>
>     'elpy (pyvenv-activate "~/.pyenv/versions/datasci")
>     )
>
> Is there anything wrong with my understanding of this macro? Any hints
> will be helpful.

Remember that in Lisp, a quoted symbol just evaluates to the symbol. So what
happens in your code is that when "python.el" is loaded, three sexps are
evaluated: the `progn`, the quoted symbol `'elpy` and the call to
`pyvenv-activate`.

The form *appears* to work because you probably load elpy whenever you open a
Python file, so you don't notice what's really going on. You'd have to
experiment with two packages that are completely independent from each other.

BTW, `with-eval-after-load` doesn't need `progn`. That was one of the reasons
for introducing `with-eval-after-load` as an alternative for `eval-after-load`.

HTH

-- 
Joost Kremers
Life has its moments

RE: [External] : Re: About the usage of `with-eval-after-load'.

[Drew Adams]

> > Based on the above explanation, it seems that only one FILE can be
> > used, but according to my tries, the following code snippet also take
> > effect:
> >   (add-hook 'python-mode-hook 'hs-minor-mode)
> >   (with-eval-after-load
> >     "python"
> >     (progn...) 'elpy (pyvenv-activate...))

Joost explained well what's going on.  In addition,
just in case it still isn't clear:

You're using only _one_ FILE arg, "python".  The 3
other args you pass correspond to the &rest arg (aka
&body defmacro arg), BODY.  So BODY is the list of
actual args: ((progn...) 'elpy (pyenv-activate...)).

Before macro `with-eval-after-load' was added, users
sometimes forgot to quote (or otherwise generate) the
second arg to the _function_ `eval-after-load' (and it
is a single arg, FORM, not an &rest list of args BODY).

That was the main reason `with-*' was introduced: for
convenience because 99% of the time FORM was a quoted
sexp, and sometimes users forgot the quote char.

Re: About the usage of `with-eval-after-load'.

[Michael Heerdegen]

Hongyi Zhao <hongyi.zhao@gmail.com> writes:

> Is there anything wrong with my understanding of this macro? Any hints
> will be helpful.

`macroexpand' your macro call.

Michael.

Re: About the usage of `with-eval-after-load'.

[Hongyi Zhao]

On Sun, Sep 19, 2021 at 8:17 AM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > Is there anything wrong with my understanding of this macro? Any hints
> > will be helpful.
>
> `macroexpand' your macro call.

`C-j' gives the following:

(macroexpand
'(with-eval-after-load
    'python
     (progn
      (define-key python-mode-map (kbd "C-c TAB") 'hs-toggle-hiding)
      (add-to-list
'python-shell-completion-native-disabled-interpreters "jupyter"))

    'elpy (pyvenv-activate "~/.pyenv/versions/datasci")))
(eval-after-load 'python (lambda nil (progn (define-key
python-mode-map ... ...) (add-to-list ... "jupyter")) 'elpy
(pyvenv-activate "~/.pyenv/versions/datasci")))

Best, HZ

Re: About the usage of `with-eval-after-load'.

[Michael Heerdegen]

Hongyi Zhao <hongyi.zhao@gmail.com> writes:

> > `macroexpand' your macro call.
>
> `C-j' gives the following:
>
> (macroexpand
> '(with-eval-after-load
>     'python
>      (progn
>       (define-key python-mode-map (kbd "C-c TAB") 'hs-toggle-hiding)
>       (add-to-list
> 'python-shell-completion-native-disabled-interpreters "jupyter"))
>
>     'elpy (pyvenv-activate "~/.pyenv/versions/datasci")))
> (eval-after-load 'python (lambda nil (progn (define-key
> python-mode-map ... ...) (add-to-list ... "jupyter")) 'elpy
> (pyvenv-activate "~/.pyenv/versions/datasci")))

... which shows that everything ends in one lambda, called after loading
"python".

Michael.

Re: About the usage of `with-eval-after-load'.

[Hongyi Zhao]

On Sun, Sep 19, 2021 at 9:51 AM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > > `macroexpand' your macro call.
> >
> > `C-j' gives the following:
> >
> > (macroexpand
> > '(with-eval-after-load
> >     'python
> >      (progn
> >       (define-key python-mode-map (kbd "C-c TAB") 'hs-toggle-hiding)
> >       (add-to-list
> > 'python-shell-completion-native-disabled-interpreters "jupyter"))
> >
> >     'elpy (pyvenv-activate "~/.pyenv/versions/datasci")))
> > (eval-after-load 'python (lambda nil (progn (define-key
> > python-mode-map ... ...) (add-to-list ... "jupyter")) 'elpy
> > (pyvenv-activate "~/.pyenv/versions/datasci")))
>
> ... which shows that everything ends in one lambda, called after loading
> "python".

So, my usage is wrong.

Best, HZ

Re: [External] : Re: About the usage of `with-eval-after-load'.

[Hongyi Zhao]

On Sat, Sep 18, 2021 at 10:56 PM Drew Adams <drew.adams@oracle.com> wrote:
>
> > > Based on the above explanation, it seems that only one FILE can be
> > > used, but according to my tries, the following code snippet also take
> > > effect:
> > >   (add-hook 'python-mode-hook 'hs-minor-mode)
> > >   (with-eval-after-load
> > >     "python"
> > >     (progn...) 'elpy (pyvenv-activate...))
>
> Joost explained well what's going on.  In addition,
> just in case it still isn't clear:
>
> You're using only _one_ FILE arg, "python".  The 3
> other args you pass correspond to the &rest arg (aka
> &body defmacro arg), BODY.  So BODY is the list of
> actual args: ((progn...) 'elpy (pyenv-activate...)).
>
> Before macro `with-eval-after-load' was added, users
> sometimes forgot to quote (or otherwise generate) the
> second arg to the _function_ `eval-after-load' (and it
> is a single arg, FORM, not an &rest list of args BODY).
>
> That was the main reason `with-*' was introduced: for
> convenience because 99% of the time FORM was a quoted
> sexp, and sometimes users forgot the quote char.

Thank you for your thoughtful further explanation, which makes me feel
that the Emacs community is indeed one of the few places in the world
where dedicated experts and masters gather. Even though my LISP
language level is still fairly rudimentary, I still have the
motivation to improve with the help of many mentors in such an
environment.

BTW, why do you write the title for your post like the following:

RE: [External] :

Best, HZ

RE: [External] : Re: About the usage of `with-eval-after-load'.

[Drew Adams]

> BTW, why do you write the title for your post like the following:
> RE: [External] :

Apologies for that noise.  There's nothing I
can do about that.  It's introduced by the
mail server used by my employer; IOW, it's
configured at the server level.

I could manually remove it from _each_ mail
I send outside the company, but I'm too lazy
to do that.