[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Byte-compilation warning in eldoc.el

From: João Távora
Subject: Re: Byte-compilation warning in eldoc.el
Date: Fri, 10 Jul 2020 16:31:18 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Thanks, fixed.  But curiously it doesn't.  You can call it (and I always
>> do call it) with one argument, as one does in CL.
> Technically, you can call it with one argument.
> But in 99% of the cases it's a really bad idea.

What's the difference to `intern'? or `intern-soft'?

>> By the way, the only reason I had to do this (I rarely use this outside
>> interactive contexts)
> Exactly: it might make sense occasionally while debugging, but is
> usually an error in code.

Not arguing but, like Drew, I wonder why.  FWIW in Common Lisp, intern,
unintern, find-symbol, etc all assume the "current package" as the thing
to operate on.

>> Separately, I also noticed that calling `package-install` for Eldoc in
>> Emacs 26.3, will _not_ load eldoc, and neither will `require`.
> Not sure what you mean with the "_not_ load" part, but as for `require`,
> it's normal because it's preloaded.

Sorry, it means two different things:

1. when you `package-install` the new eldoc 1.2.0 package in Emacs 26.3
   for the first time, it just compiles it, it doesn't load it.  We had
   witnessed this with Flymake too, remember?

2. When you shut down that Emacs session, start it again, run
   package-initialize, you _still_ don't have the new eldoc.el file
   (1.2.0) loaded.  This is only for eldoc.el, flymake.el works
   correctly in this use case.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]