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