load-prefer-newer tells load to pick the .el file if it is newer than the .elc (and vice versa, of course). This can incur a speed penalty. We need this on for emacs lisp that we write, since there is no guarantee that the compiled version is the most recent. We have been let-binding load-prefer-newer to t when loading hubs to avoid this issue. However, it seems likely that that binding does not affect autoloads. I don't see any simple/non-hacky way to deal with correctly loading the right version of autoloaded files in our config without simply setting load-prefer-newer globally. I don't expect the speed penalty to be significant. Thoughts?
@cg505, setting load-prefer-newer globally seems like a good idea to me and something which should have a minimal effect on performance, especially if we get to drop let-binding it whenever we load hubs.
load-prefer-newer
tellsload
to pick the.el
file if it is newer than the.elc
(and vice versa, of course). This can incur a speed penalty. We need this on for emacs lisp that we write, since there is no guarantee that the compiled version is the most recent. We have been let-bindingload-prefer-newer
tot
when loading hubs to avoid this issue. However, it seems likely that that binding does not affect autoloads. I don't see any simple/non-hacky way to deal with correctly loading the right version of autoloaded files in our config without simply settingload-prefer-newer
globally. I don't expect the speed penalty to be significant. Thoughts?