From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Davison Subject: Re: Src blocks fontification issue Date: Thu, 02 Sep 2010 15:48:36 -0700 Message-ID: <87eidb224b.fsf@stats.ox.ac.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=55357 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OrIaK-0008EZ-GC for emacs-orgmode@gnu.org; Thu, 02 Sep 2010 18:48:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OrIaH-0004Gb-5U for emacs-orgmode@gnu.org; Thu, 02 Sep 2010 18:48:44 -0400 Received: from markov.stats.ox.ac.uk ([163.1.210.1]:48203) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OrIaG-0004GL-UT for emacs-orgmode@gnu.org; Thu, 02 Sep 2010 18:48:41 -0400 In-Reply-To: (Julien Fantin's message of "Thu, 2 Sep 2010 20:27:27 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Julien Fantin Cc: emacs-orgmode@gnu.org Julien Fantin writes: > First congratulations on adding in-line fontification to source > blocks, that's a great addition. > > However, since I pulled those changes, a recurring issue I've been > having has become even more annoying. > > When opening an org file, some src blocks headers don't seem to get > parsed properly, and now as a result, don't get fontified. > They are functional though, since they properly get tangled, and C-c ' > performs as expected. > If I edit the header line, or the ones directly before and after it, > the block gets back to normal. > > Here is a screenshot to make things clearer, as you can see there are > no differences in formatting, and those properties drawer don't have > anything weird, just a single ID. > > http://imagebin.org/112413 > > I was meaning to post a screenshot with whitespace-mode on to stress > that there are no apparent formatting differences, but it turned out > activating it fixed the issue ! > > Not sure what I can do to further help debugging this ? Hi Julien, I don't have any clever ideas about this, so I'm just going to suggest the obvious: first a sanity check that it doesn't occur with emacs -Q. Then some sort of quasi-binary search through your emacs customisations. It looks like you're storing your emacs customisation in an Org file, so you can knock out entire trees with :tangle: no properties. Dan p.s. On a completely unrelated note, if you haven't already tried it: (add-hook 'emacs-lisp-mode-hook 'pretty-lambdas) where the `pretty-lambdas' function is in starter-kit-defuns.org at git://github.com/eschulte/emacs-starter-kit.git (defun pretty-lambdas () (font-lock-add-keywords nil `(("(?\\(lambda\\>\\)" (0 (progn (compose-region (match-beginning 1) (match-end 1) ,(make-char 'greek-iso8859-7 107)) nil)))))) > > Cheers > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode