[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: |
Tue, 19 Jul 2005 00:35:33 -0400 |
As you can see, this function sometimes returns non-nil (i.e. it says it's
found a match) but with no begin/end of match 0.
Is that incorrect? If so, why did it appear to work ok before?
Maybe the criterion for a bad match has to be written differently
to accord with the practical rules for code that used to work.
I'm tempted to just revert my patch, since it causes constant run-time
checks and trips up some pre-existing code, only in the hope of occasionally
working around some bugs that would need to be fixed anyway.
No, don't do that! Let's see if adapting a little is better.
Those bugs are rather painful.
- 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 <=
- Re: font-lock is broken, Stefan Monnier, 2005/07/19
- Re: font-lock is broken, Richard M. Stallman, 2005/07/22
- 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