-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated autoloads file is broken #111
Comments
Dave, any chance you beat me to fix this? I'll have a look in the evening... |
BTW, my el-get config is here: https://github.com/purcell/emacs.d/blob/master/init-el-get.el |
Ok my first thinking reading your el-get-sources was to get them all in:
Now, Dave, are you reading and having some time to look at the autoload issue? :) |
|
I think it's explained quite well above -- note that the problem is not specific to the diff-git recipe. Essentially, with this set of el-get recipes, start-up is fine unless the autoloads have already been generated, at which point errors like the above happen. Now, I've (since) hacked el-get locally to disable the autoload functionality completely, but I'm happy to help track down what's wrong; it'd just be good to get some pointers. |
Could we get a defvar el-get-manage-autoload (or a better name) in the main el-get, so that users can disable the feature? I'm not sure if we want to add a property to be able to do that per package like with :compile and el-get-byte-compile, though. |
Okay, so with the latest el-get I no longer get the issue when I turn off my disable-autoloads hack. I do, however, get a problem with session.el (http://www.emacswiki.org/emacs/session.el) -- it results in a loaddefs file containing So I'll go ahead and close this issue. Regarding the option to disable autoloads, I agree this would have been the wrong way to tackle this issue, but I'd like such an option anyway. At the very least, being able to define |
I'd like to be able to disable autoloads too, for giving the choice to users. That's independant of whether there's bugs in the autoloads code or not. |
Starting up emacs without el-get's new generated loaddefs file works fine for me, but once that file has been generated asynchronously, the next attempt to start emacs fails:
Here's the offending autoload:
The corresponding recipe looks like this:
but actually all the autoloads use similar relative paths.
This is with the latest dev emacs, but breaks similarly in Emacs 22.
The text was updated successfully, but these errors were encountered: