Re: kill ring menu

[Colin Walters <walters@debian.org>]

On Mon, 2002-05-06 at 02:46, Stephen J. Turnbull wrote:

> I have no statistics (nobody does) on .emacs content, but I can say
> that "how do I turn on font-lock permanently everywhere" is a Top 10
> FAQ (since XEmacs doesn't have `global-font-lock-mode'), and "who do I
> tell to add font-lock to some-unusual-mode" probably doesn't hit the
> Top 10, but it's a regular.

Right; all the Emacs and XEmacs users I personally know have enabled
font-lock globally.

> I'm a counter-example, possibly because at root I'm a Henry Ford
> acolyte: "You can have your [text] in any color you want, as long as
> it's black."  I don't like font-lock in text/plain, but I do like it
> in program source and I do like color ls.

Hm, I don't personally see, say, an *Occur* buffer as text/plain.  But
regardless, in the new implementation it's easy to disable
fontification; just

(add-hook 'occur-mode-hook 'font-lock-mode)

Or

(add-hook 'occur-mode-hook (lambda () (font-lock-mode 0))

> To be honest, my impression is that everybody likes font lock (except
> maybe Jerry Pournelle), it's just that some people want it sometimes,
> and some people want it always.

Using font-lock for all modes where possible makes things easier for
both groups of people.  Previously, you would have to hunt down a
`foo-mode-face' variable, or a `foo-mode-enable-fontification', etc.