Re: (font-lock-mode 1) does not always force font-lock

[Stefan Monnier]

>> ;; Don't turn on Font Lock mode if we don't have a display (we're running a
>> ;; batch job) or if the buffer is invisible (the name starts with a space).
>> (when (or noninteractive (eq (aref (buffer-name) 0) ?\ ))
>> (setq font-lock-mode nil))

> I propose removing the buffer-name check, at least when the argument
> to font-lock-mode is positive.

I always thought that the whole thing should be removed (i.e. including the
noninteractive check: after all, you might want to use it in batch with
ps-print or htmlize), but I never cared enough to try and convince the
rest of the developers.
So for what it's worth, I completely agree,


        Stefan