>>>>"KJ" == Kyle Jones
<kyle_jones(a)wonderworks.com> writes:
KJ> Andy Piper writes:
> This variable is set to t indicating to me that buffers should be
syntax
> highlighted by default. However, because font-lock is not loaded by default
> this has no effect. I personally believe font-lock should be loaded by
> default so that this variable does have an effect.
KJ> This sounds completely contrary to current policy. The variable's
KJ> value should default to nil so that merely loading font-lock won't
KJ> cause font-lock to attack all your buffers.
I agree with you both :-)
I.e., the default should be nil and the (featurep 'font-lock) in
fontl-hooks.el> (defun font-lock-set-defaults (&optional explicit-defaults)
fontl-hooks.el> [...]
fontl-hooks.el> (and
fontl-hooks.el> (featurep 'font-lock)
fontl-hooks.el> (if font-lock-auto-fontify
fontl-hooks.el> (not (memq major-mode font-lock-mode-disable-list))
fontl-hooks.el> (memq major-mode font-lock-mode-enable-list))
should be deleted (`font-lock-set-defaults-1' probably needs an autoload)
- Christoph