From: "Eric M. Ludlam" <eric@siege-engine.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re[2]: font-lock patch for automated edits
Date: Sun, 28 Dec 2008 08:12:22 -0500 [thread overview]
Message-ID: <200812281312.mBSDCMma011059@projectile.siege-engine.com> (raw)
In-Reply-To: <jwvod393e50.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 31 Aug 2008 02:15:31 -0400)
>>> Stefan Monnier <monnier@iro.umontreal.ca> seems to think that:
>> I have some tests for the CEDET/Semantic incremental parsing engine.
>> This test calls 'erase-buffer', and performs edits very quickly, and
>> was causing font-lock to throw errors in my tests.
>
>Do you have backtraces for those bugs?
>
>> This patch basically protects various determined regions (BEG/END)
>> from being out of bounds of a buffer. I'd guess there is a better way
>> to do it, but this allows my tests to run.
>
>I'm not sure if there's a better place to enforce the bounds, but it's
>indeed possible. Some stack traces would help figure it out,
[ ... ]
Hello,
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.
You can also use C-k on the last line in this buffer, to get the same
effect.
Thanks
Eric
--
Eric Ludlam: eric@siege-engine.com
Siege: www.siege-engine.com Emacs: http://cedet.sourceforge.net
next prev parent reply other threads:[~2008-12-28 13:12 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 [this message]
2009-04-15 21:16 ` Stefan Monnier
2009-04-15 22:57 ` Re[2]: " Eric M. Ludlam
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=200812281312.mBSDCMma011059@projectile.siege-engine.com \
--to=eric@siege-engine.com \
--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.