From: Wolfgang Jenkner <wjenkner@inode.at>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Philipp Haselwarter <philipp.haselwarter@gmx.de>,
Raphael Kubo da Costa <rakuco@FreeBSD.org>,
ding@gnus.org
Subject: Re: Font-locking broken since b895e61?
Date: Sun, 29 Jan 2012 00:23:39 +0100 [thread overview]
Message-ID: <85d3a376o4.fsf@iznogoud.viz> (raw)
In-Reply-To: <8762fx6on0.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 27 Jan 2012 18:28:35 +0100")
On Fri, Jan 27 2012, Lars Ingebrigtsen wrote:
> Wolfgang Jenkner <wjenkner@inode.at> writes:
>
>> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10063
>>
>> For some reason the bug report has been archived again, although it is
>> still not resolved (the patch I proposed was silly because it didn't
>> take into account compatibility).
>
> Do you have a new patch that would fix this issue?
I think that reverting the relevant part of
b895e61e03ce75a286e8c9d2325fcbf2266d5125 is the best solution (i.e.,
let-binding font-lock-support-mode and font-lock-mode-hook again).
However, my sending a (trivial) patch for this would be
counter-productive since you would then have to wait for my copyright
assignment :-(
Note that the OP didn't actually report a bug, just a warning message.
Wolfgang
next prev parent reply other threads:[~2012-01-28 23:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 1:42 Raphael Kubo da Costa
2012-01-25 15:33 ` Philipp Haselwarter
2012-01-25 17:14 ` Wolfgang Jenkner
2012-01-27 17:28 ` Lars Ingebrigtsen
2012-01-28 23:23 ` Wolfgang Jenkner [this message]
2012-01-27 17:27 ` Lars Ingebrigtsen
2012-01-27 21:03 ` Philipp Haselwarter
2012-01-28 19:07 ` Lars Ingebrigtsen
2012-01-27 21:30 ` Wolfgang Jenkner
2012-01-28 19:11 ` Lars Ingebrigtsen
2012-01-28 19:19 ` Lars Ingebrigtsen
2012-01-28 19:26 ` Lars Ingebrigtsen
2012-01-28 19:34 ` Lars Ingebrigtsen
2012-01-28 23:10 ` Wolfgang Jenkner
2012-01-29 0:46 ` Lars Ingebrigtsen
2012-01-29 0:53 ` Wolfgang Jenkner
2012-01-30 17:37 ` Lars Ingebrigtsen
2012-01-29 1:01 ` Raphael Kubo da Costa
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=85d3a376o4.fsf@iznogoud.viz \
--to=wjenkner@inode.at \
--cc=ding@gnus.org \
--cc=larsi@gnus.org \
--cc=philipp.haselwarter@gmx.de \
--cc=rakuco@FreeBSD.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.
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 NNTP newsgroup(s).