[Please CC me as I am not on this list -baw] I recently upgraded from XEmacs 21.1.14 to 21.4.4 and noticed there's now a breakage in font-lock mode. Both of the issues below worked fine in 21.1.14 I believe. I notice it most often in python-mode but I don't think it's specific to that mode, since I've also seen it in CC Mode. Let's say I enter the following in a C buffer (with font-lock and fast-lock enabled): -------------------- snip snip -------------------- int main() { char* foo = "hello world"; char* bar = "goodbye world -------------------- snip snip -------------------- as you're typing "goodbye world and with the cursor now sitting just after the `d' in world, you will see that the `d' is not font-locked. As soon as you type the closing quote, it does get font-locked. That's annoying, but not horrible. Now with this in the buffer: -------------------- snip snip -------------------- int main() { char* foo = "hello world"; char* bar = "goodbye world"; -------------------- snip snip -------------------- Put your cursor at the end of the `foo' line and hit backspace twice, to erase first the semicolon and then the closing quote. As soon as the closing quote gets erased, the /following/ line (i.e. the `bar' line), gets totally screwed font-locking. XEmacs will font-lock char* bar = in string face and "goodbye world" in default face, with the trailing semi in string face again. Note that retyping the quote and semi at the end of the foo line does /not/ fix the font-locking for the bar line, so you're screwed. Is this a known bug in 21.4.4, and will it be fixed soon? Thanks, -Barry