From: Alan Mackenzie <acm@muc.de>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-pretest-bug@gnu.org, 3269@emacsbugs.donarmstrong.com,
Thomas Christensen <thomasc@thomaschristensen.org>,
emacs-devel@gnu.org
Subject: Re: bug#3269: 23.0.93; C-mode text highlighting
Date: Mon, 18 May 2009 21:16:08 +0000 [thread overview]
Message-ID: <20090518211608.GC12920@muc.de> (raw)
In-Reply-To: <87iqjygy8e.fsf@cyd.mit.edu>
Hi, Yidong!
On Mon, May 18, 2009 at 12:41:21PM -0400, Chong Yidong wrote:
> Alan Mackenzie <acm@muc.de> writes:
> >> The "foo" line has lost its fontification, and this is the bug. I
> >> know what's causing it, and it _might_ be easily fixable. What's
> >> more, I don't this bug was in Emacs 22
> > OK, here is a patch for half of the problem - it now fontifies a
> > broken string in a #define properly - just that you need to type M-o
> > M-o after the change. Would you check that this works properly
> > please, Thomas!
> > The second half of the problem is to fix it so that you don't have to
> > type MoMo afterwards. Any change you'll let me do this before this
> > week's pretest, Yidong?
> Could you test these patches on some large C files, to make sure they
> don't cause any additional performance problems? But if everything
> seems OK, please go ahead and check both patches in.
I've got both bits working now. I'll do some more testing, and I expect
to be committing the whole caboodle withing 24 hours.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2009-05-18 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878wl1h5fw.fsf@ancient.thomaschristensen.org>
[not found] ` <20090514213924.GB2413@muc.de>
2009-05-18 15:06 ` bug#3269: 23.0.93; C-mode text highlighting Alan Mackenzie
2009-05-18 16:41 ` Chong Yidong
2009-05-18 21:16 ` Alan Mackenzie [this message]
2009-05-18 19:53 ` Stefan Monnier
2009-05-18 21:30 ` Alan Mackenzie
2009-05-19 2:24 ` Stefan Monnier
2009-05-19 10:26 ` Alan Mackenzie
2009-05-19 14:36 ` Stefan Monnier
2009-05-19 22:40 ` Alan Mackenzie
2009-05-20 10:31 ` Jim Meyering
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=20090518211608.GC12920@muc.de \
--to=acm@muc.de \
--cc=3269@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=thomasc@thomaschristensen.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).