all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 5490@debbugs.gnu.org, emacs-devel@gnu.org
Subject: bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro.
Date: Tue, 9 Feb 2010 20:40:08 +0000	[thread overview]
Message-ID: <20100209204008.GB2921__12878.3009517521$1265748755$gmane$org@muc.de> (raw)
In-Reply-To: <4B7158EF.6030009@swipnet.se>

Hi, Jan,

Time for a top-post.  ;-)

All your answers to my questions are consistent with a bug in
c-parse-state (don't ask!).  I recently enhanced and severely optimised
this routine (it contains a cache) to deal better with certain types of
non-unusual source files.  If this cache is getting corrupted, it could
easily foul up a buffer's indentation.

Would you try one more thing, please: when you reach this buggy state
again, would you please do

    M-: (c-state-cache-init)

, and tell me if this clears the buggy state.

Thanks!



On Tue, Feb 09, 2010 at 01:45:35PM +0100, Jan Djärv wrote:
> Ok, here are some answers.
> 
> Alan Mackenzie skrev:
> >
> >OK.  Now some more details, please!
> >
> >(i) Have you ever noticed this bug happening on earlier Emacsen, in
> >  particular Emacs 23.1?
> 
> No.
> 
> >(ii) Does this bug happen every time you use Emacs this long, or only
> >  sometimes?  If the latter, how often (10%, 50%, 90%)?
> 
> 100%.  If I just keep editing it eveentually breaks.
> 
> >(iii) Do you think there might be any connection with some of the more
> >  unusual minor modes you've got switched on?  Things like
> >  auto-encryption mode?
> >
> 
> No, this doesn't seem to have any effect.
> 
> >When Emacs reaches this broken state:
> >(iv) Are all C(++) buffers in this state, or only some?  Any correlation
> >  with how many edits have been done on a buffer, or how long it's been
> >  loaded?
> 
> It is a pre buffer breakage.  One buffer usually gets borken first, while 
> the others are ok.  It is the one that I've changed/edited the most in.
> 
> >(v) What about indentation in a freshly loaded file?
> 
> No problem.
> 
> >(vi) Will M-x c-mode or M-x c++-mode clear the problem?
> 
> Yes.
> 
> >(vii) Does reverting (M-x revert-buffer) a file fix indentation?
> 
> No.
> 
> >(viii) Does killing and reloading a file fix indentation?
> 
> Yes.
> 
> >(ix) Does intentation gradually deteriorate at around 4 hours, or does it
> >  break suddenly?
> 
> Suddenly.
> 
> >(x) Do all CC Mode buffers break at the same time, or is it a "creeping
> >  death"?
> 
> Only one at the time.
> 
> 
> >Just one other thing: Could you please post a dump of your CC Mode
> >configuration (C-c C-b in a C(++) buffer).  Thanks.
> >

[ Dump appreciated! ]

-- 
Alan Mackenzie (Nuremberg, Germany).






  parent reply	other threads:[~2010-02-09 20:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29  9:02 bug#5490: 23.1.91; CC Mode, after a while, everything is topmost-intro Jan =?UTF-8?Q?Dj=C3=A4rv
2010-01-29 11:18 ` Alan Mackenzie
     [not found] ` <20100129112201.GA3793@muc.de>
2010-02-09 12:45   ` Jan Djärv
2010-02-09 12:55     ` Jan Djärv
2010-02-09 20:40     ` Alan Mackenzie [this message]
2010-02-09 20:40     ` Alan Mackenzie
2010-02-24 12:09       ` Jan D.
2010-02-24 12:09       ` Jan D.
2010-02-25  0:59         ` Miles Bader
2010-02-25  0:59         ` Miles Bader
2010-02-26 12:58           ` Alan Mackenzie
2011-07-09  7:55         ` Jan Djärv
2016-08-18  5:01           ` Andrew Hyatt
2016-08-18  5:01           ` Andrew Hyatt
2016-08-18 14:11             ` Eli Zaretskii
2016-08-21  4:57               ` Andrew Hyatt
2016-08-21  4:57               ` Andrew Hyatt
2016-08-22 10:49                 ` Alan Mackenzie
2016-08-22 10:49                 ` Alan Mackenzie
2016-08-18 14:11             ` Eli Zaretskii
2011-07-09  7:55         ` Jan Djärv

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='20100209204008.GB2921__12878.3009517521$1265748755$gmane$org@muc.de' \
    --to=acm@muc.de \
    --cc=5490@debbugs.gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.