From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: How to track down "No heading for this item in buffer or region."? Date: Sat, 26 Jan 2013 11:51:10 +0100 Message-ID: <87r4l86wv5.fsf@bzg.ath.cx> References: <20130124123204.GB24543@boo.workgroup> <87y5fioimf.fsf@bzg.ath.cx> <20130124162311.GE24543@boo.workgroup> <87libipeot.fsf@bzg.ath.cx> <4467.1359056138@alphaville.americas.hpqcorp.net> <8738xqpbo4.fsf@bzg.ath.cx> <4630.1359091242@alphaville> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:32791) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tz3Lr-0004eZ-Hl for emacs-orgmode@gnu.org; Sat, 26 Jan 2013 05:51:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tz3Lq-00054H-JS for emacs-orgmode@gnu.org; Sat, 26 Jan 2013 05:51:11 -0500 Received: from mail-we0-x22d.google.com ([2a00:1450:400c:c03::22d]:50759) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tz3Lq-00054C-CW for emacs-orgmode@gnu.org; Sat, 26 Jan 2013 05:51:10 -0500 Received: by mail-we0-f173.google.com with SMTP id r5so578833wey.4 for ; Sat, 26 Jan 2013 02:51:09 -0800 (PST) In-Reply-To: <4630.1359091242@alphaville> (Nick Dokos's message of "Fri, 25 Jan 2013 00:20:42 -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: nicholas.dokos@hp.com Cc: emacs-orgmode , Carsten Dominik Hi Nick, Nick Dokos writes: > Not quite: the file *is* opened in a buffer (the agenda code opens all the > files, I presume with find-file-noselect), but the text properties are > not up to date. It's only when I explicitly visit the buffer > that they get updated. I updated the commit using the `font-lock-comment-face' for skipping commented scheduled/deadline lines -- it now uses comment-start-skip to skip those lines. No need to put the # at the beginning of the line, the optimization here is not significant enough IMHO. Org now relies on the general font-lock mechanism for comments, and defines comment-start etc. See `org-setup-comments-handling'. Yes, the text properties from font-lock are not always present when the buffer is not visited, you're right... things seem a bit unpredictable in this area. Thanks, -- Bastien