Alan Mackenzie writes: > there was a rather crass bug in last week's patch. Sorry. It's fixed > now, below. M-x c-toggle-parse-state-debug has been enhanced to display > messages when the state-cache is intrinsically invalid. It also now > gives a message when you {en,dis}able it. Would you try out this patch > now, please. Sorry it has taken me so long to respond. I was working in non-C-based languages for a while. today I started working in C again, and ran into issues like this: Error during redisplay: (jit-lock-function 3411) signaled (wrong-type-argument number-or-marker-p nil) c-parse-state inconsistency at 3599: using cache: nil, from scratch: ((3409 . 3599)) Old state: (setq c-state-cache '((3409 . 3599)) c-state-cache-good-pos 3599 c-state-nonlit-pos-cache '(6307 3307) c-state-nonlit-pos-cache-limit 3592 c-state-semi-nonlit-pos-cache '(3307) c-state-semi-nonlit-pos-cache-limit 3592 c-state-brace-pair-desert '(nil . 3396) c-state-point-min 1 c-state-point-min-lit-type nil c-state-point-min-lit-start nil c-state-min-scan-pos 1 c-state-old-cpp-beg nil c-state-old-cpp-end nil c-parse-state-point 3600) I have finally managed to come up with a recipe for this one. I am using "110803 rgm@gnu.org-20121105111732-ilq2sbfo09xg9i9z" with your patches. emacs -Q rwfileinfo.c M-x c-toggle-parse-state-debug C-x 4 b *Messages* RET C-s enum RET C-M-f C-p C-e , Error occurs after the comma (should be on line 197).