"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
> Unfortunately, it is not so simple. Tramp uses two different
> cookies: ";;;###autoload" and ";;;###tramp-autoload". The
former one is
> collected into auto-autoloads.el. The latter one must be collected into
> a file tramp-loaddefs.el, which is required by the other Tramp files.
What is the purpose of this division? Autoloads are not that
expensive if you don't actually call the functions.
It's the result of a code refactoring in order to minimize Tramp startup
times, and to hide Tramp as much as possible. Emacs users, who do not
use remote files, will see only tramp.el loaded. This cannot be avoided
completely, because applying "C-x C-f /s TAB" will already load Tramp in
the GNU Emacs case. Even function definitions which check, whether
another module shall be loaded, are pushed into the autoloads.
All other autoload definitions, which could also consist of whole
functions instead of the function definition, are in
tramp-loaddefs.el. Again, this file shall not be loaded for users who
feel disturbed by Tramp.
For sure, one could use a different approach. But is it a problem to
generate the tramp-loaddefs.el file inside the package repository? IIRC,
one could add local rules to the make process.
Best regards, Michael.
XEmacs-Beta mailing list