[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: font-lock is broken
From: |
Richard M. Stallman |
Subject: |
Re: font-lock is broken |
Date: |
Fri, 22 Jul 2005 00:56:11 -0400 |
The most common such problem by far is when a regexp hits a pathological
exponential-matching behavior. I wish we'd fix that one instead.
It would be good to fix that, but how? It is a consequence of the
algorithm, and even recognizing these cases would seem to be a hard
problem.
Also, they're only painful because of Emacs's lack of NMI.
What is NMI?
E.g. when C-g is pressed, record the time, and if a C-g
is pressed again 2 seconds later and the first hasn't been processed yet,
then ignore the inhibit-quit flag (i.e. set it back to nil).
I don't understand the suggestion clearly. What would it do if the
second C-g is less than two seconds later? What would it do if the
second C-g is more than two seconds later?
- font-lock is broken, Michael Kifer, 2005/07/15
- Re: font-lock is broken, Stefan Monnier, 2005/07/18
- Re: font-lock is broken, Richard M. Stallman, 2005/07/19
- Re: font-lock is broken, Stefan Monnier, 2005/07/19
- Re: font-lock is broken,
Richard M. Stallman <=
- Re: font-lock is broken, Stefan Monnier, 2005/07/22
- Re: font-lock is broken, Richard M. Stallman, 2005/07/23
- Re: font-lock is broken, Stefan Monnier, 2005/07/23
- Re: font-lock is broken, Richard M. Stallman, 2005/07/24
Re: font-lock is broken, Bill Wohler, 2005/07/19