>>>>> "jb" == Juanma Barranquero <[EMAIL PROTECTED]> writes:
[...]
jb> Obsolete *autoloaded* packages do not generate any warning on
jb> using them, so there's less incentive to switch (for people
jb> who's already using them; new users of course will see that the
jb> package is in obsolete). I agree with Richard: the error message
jb> is a good reminder to switch to better alternatives.
jb> Put another way: if they're always autoloaded, and someday we
jb> want to remove them from the distribution, it will be an abrupt
jb> change, from "working as usual" to "non-present". Not
jb> autoloading them makes this gradual: at least the user will know
jb> at some point that he is using a package considered obsolete.
I agree here---if the package had been autoloaded, I would never have
known that it was obsolete and would not have removed setting
font-lock-support-mode from my .emacs.
The problem in my mind is not that it wasn't autoloaded, it was the
stumbling to find out why. It *is* in the NEWS file, but I went first
to info looking for user-level documentation and found nothing. I think
a one liner at then end of the info note "Font Lock" something like
this would help:
JIT Lock replaces older support modes for font-lock such as
lazy-lock and fast-lock which are still available but no longer
auto-loaded.
roland
--
PGP Key ID: 66 BC 3B CD
Roland B. Roberts, PhD RL Enterprises
[EMAIL PROTECTED] 6818 Madeline Court
[EMAIL PROTECTED] Brooklyn, NY 11220
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
