Re: Reworking loaddefs.el generation

[Lars Ingebrigtsen]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> BTW, I think `autoload.el` should be extended to provide explicit
> support for these things like `mh-autoloads.el` so we don't need these
> ad-hoc rules.

Yes, my new version has that.  😀

> Eg.g. I was thinking that file-local variables should be able to include
> things like:
>
>     ;; Local Variables:
>     ;; autoload-extra-cookies: ((mh "mh-loaddefs.el") (tramp 
> "../net/tramp-loaddefs.el"))
>     ;; End:
>
> which would tell `autoload.el` to look for
> ";;;###\\(mh-\\|tramp-\\)?autoload" matches and depending on the exact
> match put the resulting entry either in the normal `loaddefs.el`, or in
> `mh-loaddefs.el` or in `tramp-loaddefs.el`.

I'm doing the latter without the former, and that seems to work fine.
That is, tramp.el currently has 

;;;###tramp-autoload
;;;###autoload

that says exactly this, so my new code just uses that.  

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no