Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org:
SL Baur <steve(a)xemacs.org> writes:
> It's probably a side-effect of eliminating the files they were
> previously dumping.
Will you be accepting patches to bring the menus back?
If they're implemented under the same conditions as eudc does it,
yes.
With vc.el it really is a problem. The current menu structure
assumes
it has most of the stuff in vc-hooks.el present to autodetect the
state. I understand one of the reasons for the whole exercise was
not to have all that stuff present?
Yes. VC has a viral load that is impossible to reverse. It might be
useful to sync it with FSF Emacs 20.3.
Or is it OK that as long a package is present it hooks itself in
through the auto-loads file... [*]
For now, yes.
May be just a "VC" menu with an initial "load VC
hooks" entry would be
the best solution?
Yes, that sounds good and leaves it to the discretion of the user
without being unnecesarily cumbersome.
P.S I am partial to [*] because I want everything that can be
enabled
automatically to work without user intervention. However there current
is not a mechanism to prevent a package from loading if it is present.
There is a mechanism. If you arrange to have a
(provide 'vc-autoloads)
executed before the autoloads file is read, it will suppress loading.
(This would happen when the sysadmins have installed the vc package
but the user hates it).
Right. We should be able to accomodate that case. For VC, your
suggestion of a `load VC hooks' or attaching a menu with only a
`initialize VC' menuitem (which loads VC hooks and replaces that
menuitem with the full menu) might be the best approach.