Re: Tramp modified-p behaviour
Michael Albinus writes:
It's the result of a code refactoring in order to minimize Tramp
startup
times, and to hide Tramp as much as possible.
That's what I thought. But AFAICS, it can't work. Sure, you can
reduce loaded code volume this way, but it doesn't "hide" Tramp; the
same entry points will be visible except perhaps for the most basic
non-users. The only way to hide Tramp is to actually reduce the
number of entry points.
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.
One can always do that kind of thing. Unfortunately, I don't have
time for it for the next few months.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta