[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: kill ring menu

From: Colin Walters
Subject: Re: kill ring menu
Date: 10 Jun 2002 01:39:55 -0400

On Mon, 2002-06-10 at 00:29, Miles Bader wrote:
> Colin Walters <address@hidden> writes:
> > One other thing I forgot to mention that you have to do is set up
> > `font-lock-defaults' so that global font-lock knows to turn on.  I just
> > added a bit to the elisp manual about how to do this; basically you need
> > to add:
> > 
> > (set (make-local-variable 'font-lock-defaults)
> >           '(nil t nil nil nil (font-lock-core-only . t)))
> The stuff with `font-lock-core-only' seems ugly.

Yes, it is, somewhat.  In this case though, the passing
`font-lock-core-only' is just an optimization; it's not strictly
necessary.  You still need to set `font-lock-defaults' though.

> Since using `char-property-alias-alist' is so absurdly cheap, why not
> just make global-font-lock-mode turn on font-lock-mode for _every_
> buffer, but only load the hairy stuff if `font-lock-defaults' is
> non-nil?

Something about doing that made me nervous.  Can anyone see a problem
with it?

I will try it though, and see if I run into any problems.

> Then modes wouldn't have to do anything to use font-locking, just start
> adding the property to their buffer.

That would be ideal, I agree.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]