GNU bug report logs - #11749
24.1; C-mode indentation gives wrong-type-argument error.

Previous Next

Packages: emacs, cc-mode;

Reported by: storm <at> cua.dk (Kim F. Storm)

Date: Tue, 19 Jun 2012 20:50:02 UTC

Severity: normal

Merged with 9957, 13385

Found in versions 24.0.90, 24.1

Done: Alan Mackenzie <acm <at> muc.de>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Michael Welsh Duggan <mwd <at> cert.org>
To: Alan Mackenzie <acm <at> muc.de>
Cc: Michael Welsh Duggan <md5i <at> md5i.com>, "11749 <at> debbugs.gnu.org" <11749 <at> debbugs.gnu.org>, Kim Storm <storm <at> cua.dk>
Subject: bug#11749: Acknowledgement (24.1; C-mode indentation gives wrong-type-argument error.)
Date: Fri, 21 Sep 2012 13:47:15 -0400
Michael Welsh Duggan <mwd <at> cert.org> writes:

> Michael Welsh Duggan <mwd <at> cert.org> writes:
>
>>>> There is generally no way to re-create it, so I've stopped reporting
>>>> these.  I wish there were some way to record all actions in c-mode
>>>> buffers such that they could be saved and re-played when this type of
>>>> problem happens.  If there were some sort of debug flag I could turn
>>>> on, I would turn it on by default and hopefully be able to catch some
>>>> useful information.
>>>
>>> M-x c-toggle-parse-state-debug
>>>
>>> (or (c-toggle-parse-state-debug 1) in your .emacs).  Warning: variable
>>> `c-debug-parse-state' is not buffer local.  I wrote this on 19th October
>>> last year to help sort out the bug you reported a little earlier.  :-)
>>>
>>> It works by calculating c-parse-state twice for each call - The first
>>> time normally, then again with the internal state bound to "newly
>>> initialised".  If the the two results differ, they are printed to
>>> *Messages*, together with the saved previous state.  If this does
>>> trigger, please note any recent buffer changes.  It may make editing
>>> intolerably slow.
>>
>> I will turn this on.

I turned this on, and inserted a (ding) where cc-mode outputs an
inconsistency message.  I can barely stand to edit code now, due to
what seem to be almost every key press causing a beep.  Have you made
any progress here, or do you need more data?

-- 
Michael Welsh Duggan
(mwd <at> cert.org)




This bug report was last modified 12 years and 107 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.