martin rudalics skrev:
>> I see this too a lot, even in plain C files. A backtrace when this
>> happen looks like this:
>>
>> Debugger entered--Lisp error: (scan-error "Containing expression ends
>> prematurely" 107612 107612)
>> scan-lists(107699 -1 0)
>> forward-list(-1)
>> backward-list(1)
>> beginning-of-defun-raw(nil)
>> beginning-of-defun()
>> c-get-fallback-start-pos(108117)
>> c-parse-state()
>> c-electric-semi&comma(nil)
>> call-interactively(c-electric-semi&comma)
>> call-last-kbd-macro(nil kmacro-loop-setup-function)
>> kmacro-call-macro(nil nil)
>> kmacro-end-and-call-macro(nil)
>> call-interactively(kmacro-end-and-call-macro)
>>
>> Usually moving the cursor up a few lines, hitting tab to indent that
>> line, and then move back to the offending line cures it.
>
> It's a consequence of the recent change to `beginning-of-defun-raw'.
> Compare the threads "font-locking and open parens in column 0" and
> "emacs hangs in jit-lock".
Ok. IMHO this must be fixed before release, editing C/C++ is very hard with
this error.
I haven't been able to find a short test case that triggers it though.
Jan D.
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
