all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Extensive changes during pretest
Date: Sun, 24 Feb 2008 08:20:54 +0000	[thread overview]
Message-ID: <20080224082054.GA1073@muc.de> (raw)
In-Reply-To: <uk5kvm1ge.fsf@gnu.org>

Hi, Eli,

On Sun, Feb 24, 2008 at 06:18:41AM +0200, Eli Zaretskii wrote:
> > Date: Sat, 23 Feb 2008 21:52:35 +0000
> > Cc: emacs-devel@gnu.org
> > From: Alan Mackenzie <acm@muc.de>

> > >   2008-02-19  Alan Mackenzie  <acm@muc.de>

> > > 	  Set of changes so that "obtrusive" syntactic elements in a
> > > 	  C/C++/ObjC preprocessor line (e.g. an unbalanced string quote
> > > 	  or unmatched paren) don't interact syntactically with stuff
> > > 	  outside the CPP line.

> > [ .... ]

> > This was to fix a bug reported by a user.  I decided to fix it
> > properly, rather than with some temporary cludge (they rarely work
> > well).  The bug report was:

> Was that bug really that grave to warrant such extensive changes at the
> last moment?

I think it was.  The only workaround would require the user to change his
source code (or use a different editor).  Possibly I was mistaken.   

> The bug was in incorrect fontification, right?

Incorrect fontification over the entire buffer after the #warning line
(or at least until the next apostrophe within a comment).  It also made
M-[ae] (statement/sentence movement) and C-M-[ae] (function movement) and
probably quite a lot else (anything involving the syntax table) go
haywire.

-- 
Alan Mackenzie (Nuremberg, Germany).




  reply	other threads:[~2008-02-24  8:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 11:40 Extensive changes during pretest Eli Zaretskii
2008-02-23 15:00 ` Chong Yidong
2008-02-23 17:58   ` Minor Gnus changes for EMACS 22.2 pretest (was: Extensive changes during pretest) Reiner Steib
2008-02-24  0:06   ` Extensive changes during pretest Dan Nicolaescu
2008-02-23 15:52 ` Stefan Monnier
2008-02-23 19:46 ` Glenn Morris
2008-02-23 21:13   ` Eli Zaretskii
2008-02-23 21:52 ` Alan Mackenzie
2008-02-24  4:18   ` Eli Zaretskii
2008-02-24  8:20     ` Alan Mackenzie [this message]
2008-02-24 19:31       ` Juri Linkov
2008-02-24 20:11         ` Alan Mackenzie
2008-02-24 19:38       ` Eli Zaretskii
2008-02-24 20:03         ` Alan Mackenzie
2008-02-24 20:09           ` Eli Zaretskii
2008-02-24 20:42             ` Alan Mackenzie
2008-02-24 21:52               ` Eli Zaretskii
2008-02-24 22:34                 ` Alan Mackenzie
2008-02-24  0:53 ` Richard Stallman
2008-02-25 16:24 ` Michael McNamara
2008-02-25 19:54   ` Chong Yidong
2008-02-25 20:34   ` Eli Zaretskii

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=20080224082054.GA1073@muc.de \
    --to=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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 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.