[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Font-lock in COMINT modes
From: |
Richard Stallman |
Subject: |
Re: Font-lock in COMINT modes |
Date: |
Tue, 12 Dec 2006 09:29:07 -0500 |
My presumption is that '(nil) and nil must differ in some other
way (aside from the unintended side effect of changing the default
non-keyword fontification), since the original change from Sept.
explicitly bound f-l-defaults non-nil, which by inference suggests nil and
'(nil t) would exhibit this same difference, whatever it is.
It affects facemenu. I am pretty sure that was my motive
for making the change.
However, if it also makes things a lot slower, that is not good.
Has some font lock expert verified that this is really happening?
If so, we should set up a way to turn off facemenu for faces while not
turning on the Font Lock mechanism unnecessarily.
One way is for Font Lock to notice the value (nil t)
specially and not turn on the mechanism.
Another way is to have another variable to disable the faces menu
with. That way is very safe.
- Font-lock in COMINT modes, JD Smith, 2006/12/06
- Re: Font-lock in COMINT modes, JD Smith, 2006/12/07
- Re: Font-lock in COMINT modes, JD Smith, 2006/12/07
- Re: Font-lock in COMINT modes, Richard Stallman, 2006/12/08
- Re: Font-lock in COMINT modes, JD Smith, 2006/12/08
- Re: Font-lock in COMINT modes, Stefan Monnier, 2006/12/08
- Re: Font-lock in COMINT modes, JD Smith, 2006/12/11
- Re: Font-lock in COMINT modes,
Richard Stallman <=
- Message not available
- Re: Font-lock in COMINT modes, Richard Stallman, 2006/12/18
- Re: Font-lock in COMINT modes, Chong Yidong, 2006/12/18
- Re: Font-lock in COMINT modes, Stefan Monnier, 2006/12/18
- Re: Font-lock in COMINT modes, Richard Stallman, 2006/12/20
- Re: Font-lock in COMINT modes, Stefan Monnier, 2006/12/20
- Re: Font-lock in COMINT modes, Richard Stallman, 2006/12/09