From: "Eric M. Ludlam" <eric@siege-engine.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re[2]: font-lock patch for automated edits
Date: Wed, 15 Apr 2009 18:57:54 -0400 [thread overview]
Message-ID: <200904152257.n3FMvsBq020433@projectile.siege-engine.com> (raw)
In-Reply-To: <jwvbpqxaadx.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 15 Apr 2009 17:16:19 -0400)
>>> Stefan Monnier <monnier@IRO.UMontreal.CA> seems to think that:
>> I updated my version of Emacs from CVS recently, and this problem
>> still occurs. I also have a simplified reproduction step. Start with
>> this C++ file:
>
>> ----------
>> /* A comment */
>> /*
>> * A multi-line comment
>> */
>> -----------
>
>> Make sure font lock has fontified this entire buffer.
>> Mark the entirety of the multi-line comment, and use C-w to kill the
>> region. Font lock will throw an error and stop auto-updating.
>
>I see now. It appears to be a bug in c-extend-after-change-region
>(assigned to font-lock-extend-after-change-region-function) which
>returns a region that extends past the end of the buffer.
>
>Alan, can you take a look at it? In the above recipe, it helps to do:
>M-: (setq fnt-lock-support-mode nil debug-on-error t) RET and then
>toggle font-lock-mode OFF and back ON before doing the C-w.
Thanks Stefan. My .emacs is so old I had old font-lock-support stuff
in it trying to allow functionality between Emacs 20 and 21 and
various support modes that I think has the effect your M-: line above
creates.
Without the old config, thus enabling jit-lock-mode, my automated
editing test suites work fine when font lock is enabled.
Eric
--
Eric Ludlam: eric@siege-engine.com
Siege: www.siege-engine.com Emacs: http://cedet.sourceforge.net
prev parent reply other threads:[~2009-04-15 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 14:56 font-lock patch for automated edits Eric M. Ludlam
2008-08-31 6:15 ` Stefan Monnier
2008-09-01 3:07 ` Re[2]: " Eric M. Ludlam
2008-12-28 13:12 ` Eric M. Ludlam
2009-04-15 21:16 ` Stefan Monnier
2009-04-15 22:57 ` Eric M. Ludlam [this message]
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=200904152257.n3FMvsBq020433@projectile.siege-engine.com \
--to=eric@siege-engine.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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.