From: Kyle Meyer <kyle@kyleam.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: src code fontification in org 8.3
Date: Sun, 14 Feb 2016 23:52:01 -0500 [thread overview]
Message-ID: <87wpq6bmoe.fsf@kyleam.com> (raw)
In-Reply-To: <m2twlbc57p.fsf@andrew.cmu.edu> (John Kitchin's message of "Sun, 14 Feb 2016 17:11:38 -0500")
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> I have this set:
>
> (setq org-src-fontify-natively t)
>
> but the code blocks are all black text.
>
> Is there a known issue with a transition from 8.2.10 to 8.3 that would
> affect fontification? or some previous setting that would interfere with
> it? Thanks,
Are you using a developmental build of Emacs? If so, it should be fixed
if you update your build.
Here are the details from Org's eb3b104 (org-src: Use font-lock-ensure
to highlight blocks, 2016-01-29):
* lisp/org-src.el (org-src-font-lock-fontify-block): Use
org-font-lock-ensure instead of font-lock-fontify-buffer.
This replacement has previously been made (f36b19e, d81e6b5) and then reverted
(99f9999, 003a0f1) twice because source blocks were not being reliably
highlighted when font-lock-ensure was used instead of
font-lock-fontify-buffer. This was due to a bug in font-lock-ensure
that has now been fixed (see Emacs's 21beb19 and bug#22399).
font-lock-ensure was introduced after Emacs 24.5, so this issue only
pertains to users with a developmental version of Emacs.
--
Kyle
next prev parent reply other threads:[~2016-02-15 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 22:11 src code fontification in org 8.3 John Kitchin
2016-02-15 4:52 ` Kyle Meyer [this message]
2016-02-15 17:40 ` John Kitchin
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpq6bmoe.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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/org-mode.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).