unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 6343@debbugs.gnu.org
Subject: bug#6343: Log-edit font lock changes lead to loop
Date: Thu, 03 Jun 2010 13:36:50 -0400	[thread overview]
Message-ID: <yxqiq60rpal.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <874ohk5933.fsf@stupidchicken.com> (Chong Yidong's message of "Thu\, 03 Jun 2010 13\:17\:52 -0400")

Chong Yidong <cyd@stupidchicken.com> writes:

> I had the following text in my kill ring:
>
>   * cedet/semantic/lex-spp.el
>   (semantic-lex-spp-table-write-slot-value): Instead of erroring on
>   invalid values during save, just save a nil (Bug#6324).
>
> From VC-dir, I marked some files and typed "v" to commit them.  In the
> log edit buffer, I type "C-y" to attempt to yank into the buffer.  Emacs
> became unresponsive to all keyboard input.  According to the debugger,
> Emacs is looping on `jit-lock-fontify-now'.
>
>
> If I revert the following change, the problem goes away.
>
> 22010-06-02  Dan Nicolaescu  <dann@ics.uci.edu>
>
>   * log-edit.el (log-edit-font-lock-keywords): Make group 4 match lax.

The motivation for the above change was that the *Messages* would get a lot of errors of the form:
(from memory, so the wording is not exactly this)

Error in redisplay, could not match (4 font-lock-warning-face)






  reply	other threads:[~2010-06-03 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 17:17 bug#6343: Log-edit font lock changes lead to loop Chong Yidong
2010-06-03 17:36 ` Dan Nicolaescu [this message]
2010-06-04  1:40 ` Juanma Barranquero
2010-06-04  2:12   ` Lennart Borgman
2010-06-04 10:15     ` Juanma Barranquero
2010-06-04 10:34       ` Lennart Borgman
2011-07-12  8:10       ` Glenn Morris

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=yxqiq60rpal.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=6343@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    /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).