From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Gerlach Subject: Loss of Fontification partway through file Date: Wed, 18 Jun 2014 20:41:55 -0400 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c29df0d11b1704fc25a489 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49662) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxQQQ-0008Te-FI for emacs-orgmode@gnu.org; Wed, 18 Jun 2014 20:41:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WxQQP-0007ry-3p for emacs-orgmode@gnu.org; Wed, 18 Jun 2014 20:41:58 -0400 Received: from mail-qg0-x235.google.com ([2607:f8b0:400d:c04::235]:52362) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxQQO-0007rs-Tq for emacs-orgmode@gnu.org; Wed, 18 Jun 2014 20:41:57 -0400 Received: by mail-qg0-f53.google.com with SMTP id i50so1506397qgf.12 for ; Wed, 18 Jun 2014 17:41:56 -0700 (PDT) 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: emacs-orgmode@gnu.org --001a11c29df0d11b1704fc25a489 Content-Type: text/plain; charset=UTF-8 Hello List, I just converted my init file to an init.org to load with babel. I prefer to view the source blocks with font lock (org-src-fontify-natively). My problem is that certain parts of the file don't show the fontification. I had a lot of trouble narrowing down my init to provide a good MWE/recipe for the behavior, but I can reproduce it with: $ emacs -q test.org M-: (package-initialize) RET M-: (setq org-src-fontify-natively t) RET The src block in the level 2 headings of the third heading below doesn't fontify for me. Minor changes (even changing one of the commented load paths) fix the issue, but not in any way that seems predictable to me. If I move headings around in init.org, the exact location where fontification stops varies, but once it stops, all remaining src blocks are un-fontified. Am I violating some sort of convention that is hanging up the fontification code? Thanks for any tips, Jake --------test.org--------------------- * Heading with some add-to-list's (some commented) #+BEGIN_SRC emacs-lisp :tangle yes (add-to-list 'foo "bar") ;; (add-to-list 'load-path "~/.emacs.d/jake-lisp/moos-mode/trunk") ;; (add-to-list 'load-path "~/.emacs.d/jake-lisp/moos-mode/devel") (add-to-list 'load-path "/home/jacob/.emacs.d/jake-lisp/ai-moos/devel") #+END_SRC * Heading with Note Note: Loading and initializing of package is done in .emacs to ensure that the newer version of org is loaded from elpa in favor of the version distributed with emacs #+BEGIN_SRC emacs-lisp :tangle yes (add-to-list 'package-archives '("marmalade" . "http://marmalade-repo.org/packages/")) #+END_SRC * Offending section ** Offending subsection #+BEGIN_SRC emacs-lisp :tangle yes (message "foobar") #+END_SRC ------------------------------------- org-version is a variable defined in `org.el'. Its value is "8.2.6" emacs-version is a variable defined in `C source code'. Its value is "24.3.1" --001a11c29df0d11b1704fc25a489 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello List,

I just converted= my init file to an init.org to load with b= abel. I
prefer to view the source blocks with font lock
(org-src-fontify-natively). My problem is that certain parts of the
file don't show the fontification.

I had a = lot of trouble narrowing down my init to provide a good
MWE/recip= e for the behavior, but I can reproduce it with:=C2=A0

$ emacs -q test.org
M-: (package-initialize) RET
M-: (setq org-src-fontify-natively t) RET

The src block in the level 2 headings of the third head= ing below
doesn't fontify for me. Minor changes (even changin= g one of the
commented load paths) fix the issue, but not in any = way that seems
predictable to me.

If I move headings around = in init.org, the exact location where
=
fontification stops varies, but once it stops, all remaining src
blocks are un-fontified.

Am I violating some = sort of convention that is hanging up the
fontification code?

Thanks for any tips,
Jake

--------test.org----------= -----------
* Headin= g with some add-to-list's (some commented)
#+BEGIN_SRC emacs-lisp :tangle yes
(add-to-list 'foo "bar&= quot;)
;; (add-to-li= st 'load-path "~/.emacs.d/jake-lisp/moos-mode/trunk")<= /div>
;; (add-to-list 'load-path &= quot;~/.emacs.d/jake-lisp/moos-mode/devel")
(add-to-list 'load-path "/home/jacob/= .emacs.d/jake-lisp/ai-moos/devel")
#+END_SRC
* Heading with Note
Note: Loading a= nd initializing of package is done in .emacs to
ensure that the newer version of org is loaded from elpa= in favor of
the version distributed with em= acs
#+BEGIN_SRC emacs-lisp :tangle yes
(add-to-list 'package-archives=
=C2=A0 =C2=A0 '("marmal= ade" .
=C2=A0 = =C2=A0 =C2=A0 "http://= marmalade-repo.org/packages/"))
#+END_SRC
* Offending section
** Offending subsection
#+BEGIN_SRC emacs-lisp :tangle yes
(message "foobar")
=
#+END_SRC
-------------------------------------

org-version is a va= riable defined in `org.el'.
Its value is "8.2.6"

emacs-version is a = variable defined in `C source code'.
Its value is "24.3.1"

<= /div>
--001a11c29df0d11b1704fc25a489-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Re: Loss of Fontification partway through file Date: Thu, 19 Jun 2014 09:34:18 +0200 Message-ID: <87y4wtcpz9.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53896) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxWri-0006D0-Qd for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 03:34:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WxWrd-00023m-Rz for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 03:34:34 -0400 Received: from plane.gmane.org ([80.91.229.3]:47115) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxWrd-00023i-Kp for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 03:34:29 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WxWrc-0008N1-Ht for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 09:34:28 +0200 Received: from e178190139.adsl.alicedsl.de ([85.178.190.139]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 Jun 2014 09:34:28 +0200 Received: from tjolitz by e178190139.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 Jun 2014 09:34:28 +0200 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: emacs-orgmode@gnu.org Jacob Gerlach writes: > Hello List, > > I just converted my init file to an init.org to load with babel. I > prefer to view the source blocks with font lock > (org-src-fontify-natively). My problem is that certain parts of the > file don't show the fontification. > > I had a lot of trouble narrowing down my init to provide a good > MWE/recipe for the behavior, but I can reproduce it with: > > $ emacs -q test.org > M-: (package-initialize) RET > M-: (setq org-src-fontify-natively t) RET > > The src block in the level 2 headings of the third heading below > doesn't fontify for me. Minor changes (even changing one of the > commented load paths) fix the issue, but not in any way that seems > predictable to me. > > If I move headings around in init.org, the exact location where > fontification stops varies, but once it stops, all remaining src > blocks are un-fontified. > > Am I violating some sort of convention that is hanging up the > fontification code? > > Thanks for any tips, > Jake > > --------test.org--------------------- > * Heading with some add-to-list's (some commented) > #+BEGIN_SRC emacs-lisp :tangle yes > (add-to-list 'foo "bar") > ;; (add-to-list 'load-path "~/.emacs.d/jake-lisp/moos-mode/trunk") > ;; (add-to-list 'load-path "~/.emacs.d/jake-lisp/moos-mode/devel") > (add-to-list 'load-path > "/home/jacob/.emacs.d/jake-lisp/ai-moos/devel") > #+END_SRC > * Heading with Note > Note: Loading and initializing of package is done in .emacs to > ensure that the newer version of org is loaded from elpa in favor of > the version distributed with emacs > #+BEGIN_SRC emacs-lisp :tangle yes > (add-to-list 'package-archives > '("marmalade" . > "http://marmalade-repo.org/packages/")) > #+END_SRC > * Offending section > ** Offending subsection > #+BEGIN_SRC emacs-lisp :tangle yes > (message "foobar") > #+END_SRC > ------------------------------------- > > org-version is a variable defined in `org.el'. > Its value is "8.2.6" > > emacs-version is a variable defined in `C source code'. > Its value is "24.3.1" The MWE (with native fontification -> t) looks ok for me, the only fontification issue I see (and not only in your MWE) is that headline ,---- | * Heading with some add-to-list's (some commented) `---- looses its font due to the "list" in it -> '(some commented)'. I see that often in my Org files - as soon as I type parens in a headline it turn white. ,---- | Org-mode version 8.2.7 (release_8.2.7-1096-g23496c @ | /usr/share/emacs/24.3/lisp/org/lisp/) `---- -- cheers, Thorsten From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Gerlach Subject: Re: Loss of Fontification partway through file Date: Thu, 19 Jun 2014 05:47:54 -0400 Message-ID: References: <87y4wtcpz9.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113369385e227204fc2d4539 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49764) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxYwm-00086l-8z for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 05:47:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WxYwl-0004GC-1y for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 05:47:56 -0400 Received: from mail-qg0-x22a.google.com ([2607:f8b0:400d:c04::22a]:40902) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxYwk-0004G7-TN for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 05:47:54 -0400 Received: by mail-qg0-f42.google.com with SMTP id e89so1923644qgf.1 for ; Thu, 19 Jun 2014 02:47:54 -0700 (PDT) In-Reply-To: <87y4wtcpz9.fsf@gmail.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: Thorsten Jolitz Cc: emacs-orgmode@gnu.org --001a113369385e227204fc2d4539 Content-Type: text/plain; charset=UTF-8 > > The MWE (with native fontification -> t) looks ok for me, Thanks for taking time to check this. I should note that if I find a new file (test.org) and yank the MWE, it is fontified correctly, but if I save and kill the buffer and then find the file again, that is when the problem occurs. In general, if I make a change that brings back the fontification, it doesn't disappear again until freshly finding the file. > the only > fontification issue I see (and not only in your MWE) is that headline > > ,---- > | * Heading with some add-to-list's (some commented) > `---- > > looses its font due to the "list" in it -> '(some commented)'. > I see that often in my Org files - as soon as I type parens in a > headline it turn white. > > I do not observe the same. Since it is outside of an emacs-lisp source block, why would it be interpreted as a "list"? > > > ,---- > | Org-mode version 8.2.7 (release_8.2.7-1096-g23496c @ > | /usr/share/emacs/24.3/lisp/org/lisp/) > `---- > > -- > cheers, > Thorsten > > Thanks, Jake --001a113369385e227204fc2d4539 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The MWE (with native fontification -> t) looks ok for me, <= div>Thanks for taking time to check this. I should note that if I find a ne= w file (test.org) and yank the MWE, it is f= ontified correctly, but if I save and kill the buffer and then find the fil= e again, that is when the problem occurs. In general, if I make a change th= at brings back the fontification, it doesn't disappear again until fres= hly finding the file.
=C2=A0
the only
fontification issue I see (and not only in your MWE) is that headline

,--= --
| * Heading with some add-to-list's (some commented)
`----

looses its font due to the "list" in it -> '(some commente= d)'.
I see that often in my Org files - as soon as I type parens in a
headline it turn white.

I do not observe the same. Since it is outside of an = emacs-lisp source block, why would it be interpreted as a "list"?=
=C2=A0

,----
| Org-mode version 8.2.7 (release_8.2.7-1096-g23496c @
| /usr/share/emacs/24.3/lisp/org/lisp/)
`----

--
cheers,
Thorsten

Thanks,
Jake=C2=A0
--001a113369385e227204fc2d4539-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Re: Loss of Fontification partway through file Date: Thu, 19 Jun 2014 12:39:04 +0200 Message-ID: <87tx7hp4jb.fsf@gmail.com> References: <87y4wtcpz9.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59319) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxZkd-0000Ms-79 for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 06:39:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WxZkT-0000Us-6U for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 06:39:27 -0400 Received: from plane.gmane.org ([80.91.229.3]:54434) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxZkT-0000Ue-02 for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 06:39:17 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WxZkR-00042y-Gy for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 12:39:15 +0200 Received: from e178190139.adsl.alicedsl.de ([85.178.190.139]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 Jun 2014 12:39:15 +0200 Received: from tjolitz by e178190139.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 Jun 2014 12:39:15 +0200 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: emacs-orgmode@gnu.org Jacob Gerlach writes: > The MWE (with native fontification -> t) looks ok for me, > > Thanks for taking time to check this. I should note that if I find a > new file (test.org) and yank the MWE, it is fontified correctly, but > if I save and kill the buffer and then find the file again, that is > when the problem occurs. In general, if I make a change that brings > back the fontification, it doesn't disappear again until freshly > finding the file. I did this too (save and kill the buffer and then find the file again), again no issues, and even the issue described below disappeared ;) What you describe reminds me a bit of fontification issues with outshine.el, only that its just the opposite. When I find a file with e.g .el extension (having stored `outline-minor-mode' in the major-mode hook, and `outshine-hook-function' in the outline-minor-mode hook), the buffer is fontified correctly right away. But when I write some (outshine-style structured) content in a temp buffer in e.g. fundamental-mode, and then call `emacs-lisp-mode' on that buffer, the org-mode like headline-fontification is not there immediately, I first have to do something (visibility cycling, add a char or so...), then the 1st level headers turn blue ... > the only > fontification issue I see (and not only in your MWE) is that > headline > > > > ,---- > | * Heading with some add-to-list's (some commented) > > `---- > > looses its font due to the "list" in it -> '(some commented)'. > I see that often in my Org files - as soon as I type parens in a > headline it turn white. > > I do not observe the same. Since it is outside of an emacs-lisp source > block, why would it be interpreted as a "list"? no idea, but this 'unfontification' of headline with '(...)' in them happens quite frequently for me. -- cheers, Thorsten