Re: [O] hard coded autoload file

2013-04-26 Thread Ivan Kanis
April, 26 at 8:36 Bastien wrote: >> It sucks for me as I generate autoload with a different name. I made a >> workaround so it's fine. > > Why do you generate autoloads with a different name? I do my own packaging. I started before ELPA and el-get existed. I was dissatisfied with the Debian way.

Re: [O] hard coded autoload file

2013-04-25 Thread Bastien
Hi Ivan, Ivan Kanis writes: > It seems each file has the name of the autoload file hard coded at the > end. > > For example at the end org-element.el: > > ;; Local variables: > ;; generated-autoload-file: "org-loaddefs.el" > ;; End: > > It sucks for me as I generate autoload with a different nam

[O] hard coded autoload file

2013-04-25 Thread Ivan Kanis
Hello, It seems each file has the name of the autoload file hard coded at the end. For example at the end org-element.el: ;; Local variables: ;; generated-autoload-file: "org-loaddefs.el" ;; End: It sucks for me as I generate autoload with a different name. I made a workaround so it's fine. I