GNU bug report logs - #6465
Error during redisplay: (error No match 4 in highlight (4 font-lock-warning-face))

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6465 in the body.
You can then email your comments to 6465 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #3 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Dan Nicolaescu <dann <at> gnu.org>
To: bug-gnu-emacs <at> gnu.org
Subject: Error during redisplay: (error No match 4 in highlight (4
	font-lock-warning-face))
Date: Sat, 19 Jun 2010 02:51:17 -0400

When using C-x v v to check something in, there's a lot of messages
like this in the *Messages* buffer:

Error during redisplay: (error No match 4 in highlight (4 font-lock-warning-face)) [3 times]

Probably the cause is this change to `log-edit-font-lock-keywords':

2010-04-21  Stefan Monnier  <monnier <at> iro.umontreal.ca>

            Make the log-edit comments use RFC822 format throughout.

            * vc.el (vc-checkin, vc-modify-change-comment):
            Adjust to new vc-start/finish-logentry.
            (vc-find-conflicted-file): New command.
            (vc-transfer-file): Adjust to new vc-checkin.
            (vc-next-action): Improve scoping.

            * vc-hg.el (vc-hg-log-edit-mode): Remove.
            (vc-hg-checkin): Remove extra arg.  Use log-edit-extract-headers.

            * vc-git.el (vc-git-log-edit-mode): Remove.
            (vc-git-checkin): Remove extra arg.  Use log-edit-extract-headers.
            (vc-git-commits-coding-system): Rename from git-commits-coding-system.

            * vc-dispatcher.el (vc-log-edit): Shorten names for log-edit-show-files.
            (vc-start-logentry): Remove argument `extra'.
            (vc-finish-logentry): Remove extra args.

            * vc-bzr.el (vc-bzr-log-edit-mode): Remove.
            (vc-bzr-checkin): Remove extra arg.  Use log-edit-extract-headers.
            (vc-bzr-conflicted-files): New function.

            * log-edit.el (log-edit-extra-flags)
            (log-edit-before-checkin-process): Remove.
            (log-edit-summary, log-edit-header, log-edit-unknown-header): New faces.
            (log-edit-headers-alist): New var.
            (log-edit-header-contents-regexp): New const.
            (log-edit-match-to-eoh): New function.
            (log-edit-font-lock-keywords): Use them.
            (log-edit): Insert a "Summary:" header as default.
            (log-edit-mode): Mark font-lock rules as case-insensitive.
            (log-edit-done): Cleanup headers.
            (log-view-process-buffer): Remove.
            (log-edit-extract-headers): New function to replace it.

Message #6 received at 6465 <at> debbugs.gnu.org (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: Dan Nicolaescu <dann <at> gnu.org>
Cc: 6465 <at> debbugs.gnu.org
Subject: Re: Error during redisplay: (error No match 4 in highlight (4
	font-lock-warning-face))
Date: Sun, 21 Nov 2010 19:29:32 -0500

> When using C-x v v to check something in, there's a lot of messages
> like this in the *Messages* buffer:
>
> Error during redisplay: (error No match 4 in highlight (4 font-lock-warning-face)) [3 times]
>
> Probably the cause is this change to `log-edit-font-lock-keywords':
>
> 2010-04-21  Stefan Monnier  <monnier <at> iro.umontreal.ca>
>
>             Make the log-edit comments use RFC822 format throughout.

Is this still happening to you?

Message #9 received at 6465 <at> debbugs.gnu.org (full text, mbox):

From: Dan Nicolaescu <dann <at> gnu.org>
To: Chong Yidong <cyd <at> stupidchicken.com>
Cc: 6465 <at> debbugs.gnu.org
Subject: Re: bug#6465: Error during redisplay: (error No match 4 in highlight
	(4 font-lock-warning-face))
Date: Mon, 22 Nov 2010 01:38:03 -0500

Chong Yidong <cyd <at> stupidchicken.com> writes:

>> When using C-x v v to check something in, there's a lot of messages
>> like this in the *Messages* buffer:
>>
>> Error during redisplay: (error No match 4 in highlight (4 font-lock-warning-face)) [3 times]
>>
>> Probably the cause is this change to `log-edit-font-lock-keywords':
>>
>> 2010-04-21  Stefan Monnier  <monnier <at> iro.umontreal.ca>
>>
>>             Make the log-edit comments use RFC822 format throughout.
>
> Is this still happening to you?

I can see it on the emacs-23 branch.

Message #12 received at 6465 <at> debbugs.gnu.org (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: Dan Nicolaescu <dann <at> gnu.org>
Cc: 6465 <at> debbugs.gnu.org
Subject: Re: bug#6465: Error during redisplay: (error No match 4 in highlight
	(4 font-lock-warning-face))
Date: Sat, 27 Nov 2010 14:46:31 -0500

Dan Nicolaescu <dann <at> gnu.org> writes:

>>> When using C-x v v to check something in, there's a lot of messages
>>> like this in the *Messages* buffer:
>>>
>>> Error during redisplay: (error No match 4 in highlight (4
>>> font-lock-warning-face)) [3 times]
>>>
>>> Probably the cause is this change to `log-edit-font-lock-keywords':
>>>
>>> 2010-04-21  Stefan Monnier  <monnier <at> iro.umontreal.ca>
>>>
>>>             Make the log-edit comments use RFC822 format throughout.
>>
>> Is this still happening to you?
>
> I can see it on the emacs-23 branch.

The final "\\|\\(.*\\)" in log-edit-font-lock-keywords looks bogus (it
was also the reason for the loop in Bug#6343).  Since Stefan hasn't
commented on this issue yet, I went ahead and removed that part of the
regexp.

Message #17 received at 6465 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
To: Chong Yidong <cyd <at> stupidchicken.com>
Cc: Dan Nicolaescu <dann <at> gnu.org>, 6465 <at> debbugs.gnu.org
Subject: Re: bug#6465: Error during redisplay: (error No match 4 in highlight
	(4 font-lock-warning-face))
Date: Sun, 28 Nov 2010 12:25:27 -0500

>>>>> "Chong" == Chong Yidong <cyd <at> stupidchicken.com> writes:

> Dan Nicolaescu <dann <at> gnu.org> writes:
>>>> When using C-x v v to check something in, there's a lot of messages
>>>> like this in the *Messages* buffer:
>>>> 
>>>> Error during redisplay: (error No match 4 in highlight (4
>>>> font-lock-warning-face)) [3 times]
>>>> 
>>>> Probably the cause is this change to `log-edit-font-lock-keywords':
>>>> 
>>>> 2010-04-21  Stefan Monnier  <monnier <at> iro.umontreal.ca>
>>>> 
>>>> Make the log-edit comments use RFC822 format throughout.
>>> 
>>> Is this still happening to you?
>> 
>> I can see it on the emacs-23 branch.

Thos things are trivial to solve: add a `lax' argument to the `4'
font-lock rule.

> The final "\\|\\(.*\\)" in log-edit-font-lock-keywords looks bogus (it
> was also the reason for the loop in Bug#6343).  Since Stefan hasn't
> commented on this issue yet, I went ahead and removed that part of the
> regexp.

That's OK as well, it was not an important case,


        Stefan

Message #20 received at 6465 <at> debbugs.gnu.org (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
Cc: Dan Nicolaescu <dann <at> gnu.org>, 6465 <at> debbugs.gnu.org
Subject: Re: bug#6465: Error during redisplay: (error No match 4 in highlight
	(4 font-lock-warning-face))
Date: Sat, 04 Dec 2010 16:53:17 -0500

Stefan Monnier <monnier <at> IRO.UMontreal.CA> writes:

>>> I can see it on the emacs-23 branch.
>
> Thos things are trivial to solve: add a `lax' argument to the `4'
> font-lock rule.

Adding a `lax' argument led to an infloop (Bug#6343), because of the way
log-edit-match-to-eoh works.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.