unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 5395@debbugs.gnu.org, Daniel Colascione <daniel@censorshipresearch.org>
Subject: bug#5395: cc-mode raises on typing '>' in #include
Date: Mon, 18 Jan 2010 20:03:47 +0000	[thread overview]
Message-ID: <20100118200347.GB1062@muc.de> (raw)
In-Reply-To: <87iqazpcv2.fsf@stupidchicken.com>

Hello, Yidong and Daniel,

On Mon, Jan 18, 2010 at 12:00:17PM -0500, Chong Yidong wrote:
> > Check out latest Emacs BZR.
> > Start with -Q
> > Visit an [empty] .cpp file
> > Type #include <foo>

> > After typing the closing '>', an error is raised. Here is the traceback

> Actually, I get an error as soon as I type #.

> Alan, I think this is due to your 2009-12-03 changes to the
> c-parse-state mechanism.  Could you take a look?

I feel the error is caused by the bug in

    Subject: (insert ?\n) spuriously calls before-change-functions twice.

which I reported on 2010-01-05 and have since fixed.  I haven't yet been
able to commit the fix due to not yet understanding bzr well enough.
Soon!

-- 
Alan Mackenzie (Nuremberg, Germany).






  reply	other threads:[~2010-01-18 20:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16  0:17 bug#5395: cc-mode raises on typing '>' in #include Daniel Colascione
2010-01-18 17:00 ` Chong Yidong
2010-01-18 20:03   ` Alan Mackenzie [this message]
2010-01-20 10:34 ` Alan Mackenzie
     [not found] <mailman.1514.1263626903.18930.bug-gnu-emacs@gnu.org>
2010-01-16 18:40 ` deceiver

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=20100118200347.GB1062@muc.de \
    --to=acm@muc.de \
    --cc=5395@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=daniel@censorshipresearch.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).