From: Wolfgang Jenkner <wjenkner@inode.at>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Raphael Kubo da Costa <rakuco@FreeBSD.org>, ding@gnus.org
Subject: Re: Font-locking broken since b895e61?
Date: Fri, 27 Jan 2012 22:30:17 +0100 [thread overview]
Message-ID: <85pqe4j0h0.fsf@iznogoud.viz> (raw)
In-Reply-To: <87aa596ooy.fsf@gnus.org>
On Fri, Jan 27 2012, Lars Ingebrigtsen wrote:
> Raphael Kubo da Costa <rakuco@FreeBSD.org> writes:
>
>> As an example, viewing <874o262tc7.fsf@hati.baby-gnu.org> sent to this
>> list with a revision prior to b895e61 shows me both the example Lisp
>> code and the patch at the end with syntax highlighting, whereas using
>> any Gnus revision starting with b895e61 no syntax highlighting is
>> applied.
>
> I'm unable to reproduce this. The article in question is highlighted
> nicely when I look at it with the current Emacs 24.
I tested this with bzr rev. 106952 first in my usual set-up and then in
a rather clean environment, using a different account and starting with
env NNTPSERVER=news.gmane.org emacs -Q -nw
but the bug seems still to be present, i.e., with
org-src-fontify-natively non-NIL, the stuff between #+begin_src and
#+end_src should be highlighted the way it is in emacs-lisp mode, but it
is not.
Wolfgang
next prev parent reply other threads:[~2012-01-27 21:30 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
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 [this message]
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=85pqe4j0h0.fsf@iznogoud.viz \
--to=wjenkner@inode.at \
--cc=ding@gnus.org \
--cc=larsi@gnus.org \
--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).