From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: src code fontification in org 8.3 Date: Mon, 15 Feb 2016 12:40:45 -0500 Message-ID: References: <87wpq6bmoe.fsf@kyleam.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a114b7e0c3b5da0052bd284f4 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33725) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVN8i-0000rD-3u for emacs-orgmode@gnu.org; Mon, 15 Feb 2016 12:40:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aVN8g-0003I2-Ne for emacs-orgmode@gnu.org; Mon, 15 Feb 2016 12:40:47 -0500 Received: from mail-wm0-x22a.google.com ([2a00:1450:400c:c09::22a]:37493) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aVN8g-0003Hu-8Z for emacs-orgmode@gnu.org; Mon, 15 Feb 2016 12:40:46 -0500 Received: by mail-wm0-x22a.google.com with SMTP id g62so118793914wme.0 for ; Mon, 15 Feb 2016 09:40:45 -0800 (PST) In-Reply-To: <87wpq6bmoe.fsf@kyleam.com> 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: Kyle Meyer Cc: "emacs-orgmode@gnu.org" --001a114b7e0c3b5da0052bd284f4 Content-Type: text/plain; charset=UTF-8 Thanks. A rebuild of emacs did indeed fix it. John ----------------------------------- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu On Sun, Feb 14, 2016 at 11:52 PM, Kyle Meyer wrote: > 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 > --001a114b7e0c3b5da0052bd284f4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks. A rebuild of emacs did indeed fix it.

<= div dir=3D"ltr">
John

-------------------------= ----------
Professor John Kitchin=C2=A0
Doherty Hall A207F
Departm= ent of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA= 15213
412-268-7803

On Sun, Feb 14, 2016 at 11:52 PM, Kyle Meyer= <kyle@kyleam.com> wrote:
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 wi= th
> it? Thanks,

Are you using a developmental build of Emacs?=C2=A0 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<= br> to highlight blocks, 2016-01-29):

=C2=A0 =C2=A0 * lisp/org-src.el (org-src-font-lock-fontify-block): Use
=C2=A0 =C2=A0 =C2=A0 org-font-lock-ensure instead of font-lock-fontify-buff= er.

=C2=A0 =C2=A0 This replacement has previously been made (f36b19e, d81e6b5) = and then reverted
=C2=A0 =C2=A0 (99f9999, 003a0f1) twice because source blocks were not being= reliably
=C2=A0 =C2=A0 highlighted when font-lock-ensure was used instead of
=C2=A0 =C2=A0 font-lock-fontify-buffer.=C2=A0 This was due to a bug in font= -lock-ensure
=C2=A0 =C2=A0 that has now been fixed (see Emacs's 21beb19 and bug#2239= 9).

=C2=A0 =C2=A0 font-lock-ensure was introduced after Emacs 24.5, so this iss= ue only
=C2=A0 =C2=A0 pertains to users with a developmental version of Emacs.

--
Kyle

--001a114b7e0c3b5da0052bd284f4--