Achim Gratz <strom...@nexgo.de> writes: > Also, this change again breaks installs where the autoloads file is > compressed (that was the reason for introduction of the more complicated > way to load this file that led to the introduction of the new > macro).
There is this line at the end of org-loaddefs.el: ;; no-byte-compile: t So my understanding is that org-loaddefs.el is never compressed. Under which conditions is it compressed? > In particular, when there is another org-loaddefs.el later on in the > loadpath, it will happily load that file, creating just the very problem > we were trying to avoid. That's why the user needs to add the correct load-path in his .emacs.el when using a tarball or a git clone. I made it clear in the docs. This correct load-path is shadowed by the one of an ELPA install if the user does not take care of (package-initialize) at the very beginning of his .emacs.el, but I also made it clear that users should avoid mixing two installation methods. So I think we're fine here. -- Bastien
