I see what you mean now. The RELOAD argument should not be passed when activating dependencies.
The dependency will already have been reloaded when (if) it was upgraded.
On 18 Dec 2014 12:47, "Dmitry Gutov" <
dgutov@yandex.ru> wrote:
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Aside from it, if we compare with the alternative implementation
>> suggestions, the current one reloads all dependencies, even those that
>> haven't been (re)installed during the current session.
>
> It sounds serious, but I don't understand what you're referring to.
> Can you give an example?
It reloads all dependencies of the package that is currently being
installed.
Try this:
(advice-add 'package-activate-1 :before
(lambda (pkg-desc &optional reload)
(message "package-activate-1 called with %s %s"
(package-desc-name pkg-desc) reload))
'((name . "Parrot arguments")))
Then install company (if your haven't yet), and then, with Melpa in
package archives, install company-math. You'll see this in *Messages*:
package-activate-1 called with company force
package-activate-1 called with math-symbol-lists force
package-activate-1 called with company-math force