Ville Skyttä writes:
However, at least the XEmacs doc above doesn't seem to cover how
to
auto-activate vc when opening files under control of supported version
control systems ("backends"). The way I've always done it is this in my
~/.xemacs/init.el:
(require 'vc-hooks)
I think that's still the sanctioned way to enable VC.
Some history, in case people would like to change this:
I think the -hooks.el interface came originally from the Dark Age
before auto-autoloads. The idea was to have one lightweight file that
you could always require in your init file without pulling in a huge
pile of machinery. A lot of packages used to have a -hooks.el to
intialize them from the init file.
XEmacs has a policy of not changing the UI just because a library's
entry points are autoloaded. You need to explicitly run a command to
initialize keymaps, hooks on standard commands, auto-recognize files,
and so on. Ben had partially standardized this with his concept of
behaviors, but unfortunately it's not well-documented and few
behaviors have been defined. AIUI a behavior is an interface which
allows you to specify that certain modes should always be on. What it
adds to autoloads, custom, and the older -hooks.el mechanism is (1) a
standard menu interface for *globally* enabling modes, and (2) it
knows how to enable the mode in *existing* buffers, so you don't have
to restart XEmacs.
If somebody wants to do a lot of users a medium-sized favor, you could
do worse than to study up on and document behaviors.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta