[Top][All Lists]

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

Re: feature/integrated-elpa 4f6df43 15/23: README added

From: Alain Schneble
Subject: Re: feature/integrated-elpa 4f6df43 15/23: README added
Date: Wed, 19 Oct 2016 21:33:42 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (windows-nt)

Alain Schneble <address@hidden> writes:

> Achim Gratz <address@hidden> writes:
>> Eli Zaretskii writes:
>>> I don't see why restarting won't be a solution.  If load-path was
>>> re-arranged to put the latest version of a package first, and the
>>> package's autoloads are on a file that has been regenerated, what else
>>> is missing to make restart the correct solution?
>> You are missing that the order in which all these things happen becomes
>> important.  The newer autoload can only shadow the old one if it's
>> processed _before_, likewise initializing other Emacs packages might
>> inadvertently pull in old autoloads or definitions before things have
>> been rearranged by package.el.  This is not hypothetical, all of that
>> has already happened and users have suffered from it.  When they report
>> the resulting symptoms it is extremely difficult to tease out what
>> exactly happened, in which order and why, so it also wastes the time of
>> those folks who want to help them.
> Of course.  The order of directories in load path is always relevant.
> Whatever structure we choose.

I just realized you were talking about autoloads and not load path.
Sorry.  But the conclusion doesn't change.  We just have to make sure
that the old autoload definitions are no longer loaded.


reply via email to

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