From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kyle Meyer Subject: Re: src code fontification in org 8.3 Date: Sun, 14 Feb 2016 23:52:01 -0500 Message-ID: <87wpq6bmoe.fsf@kyleam.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38023) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVB8u-0005xK-3A for emacs-orgmode@gnu.org; Sun, 14 Feb 2016 23:52:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aVB8q-000252-TQ for emacs-orgmode@gnu.org; Sun, 14 Feb 2016 23:52:12 -0500 Received: from pb-smtp0.int.icgroup.com ([208.72.237.35]:54921 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVB8q-00024v-Im for emacs-orgmode@gnu.org; Sun, 14 Feb 2016 23:52:08 -0500 In-Reply-To: (John Kitchin's message of "Sun, 14 Feb 2016 17:11:38 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: John Kitchin Cc: "emacs-orgmode@gnu.org" John Kitchin 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