From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Dan Nicolaescu <dann@gnu.org>, 6465@debbugs.gnu.org
Subject: 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 [thread overview]
Message-ID: <jwv1v66xwa0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87bp5a5z3c.fsf@stupidchicken.com> (Chong Yidong's message of "Sat, 27 Nov 2010 14:46:31 -0500")
>>>>> "Chong" == Chong Yidong <cyd@stupidchicken.com> writes:
> Dan Nicolaescu <dann@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
next prev parent reply other threads:[~2010-11-28 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 6:51 bug#6465: Error during redisplay: (error No match 4 in highlight (4 font-lock-warning-face)) Dan Nicolaescu
2010-11-22 0:29 ` Chong Yidong
2010-11-22 6:38 ` Dan Nicolaescu
2010-11-27 19:46 ` Chong Yidong
2010-11-28 17:25 ` Stefan Monnier [this message]
2010-12-04 21:53 ` Chong Yidong
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=jwv1v66xwa0.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=6465@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=dann@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 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).