Re: How to track down "No heading for this item in buffer or region."?

[Nick Dokos <nicholas.dokos@hp.com>]

Gregor Zattler <telegraph@gmx.net> wrote:

> When I move the cursor over this lines a message appears in the
> echo area:
> 
> byte-code: Before first headline at position 64 in buffer org.org [14 times]
> 
> The second line of org.org begins at character 64 in the buffer.
> It's a timestamp:
> 
> #Time-stamp: <2013-01-24 16:30:39 grfz>
> 
> Till recently this was no problem since it is a comment line.
> Obviously org-mode somehow interprets this timestamp, since the
> messages disappeared after I changed the time stamp delimiter from
> `<' and `>' respectively to `"'.  I consider this to be a bug
> since these time stamps are a standard Emacs feature and this
> line is a comment org-mode-wise.
> 
> 

I am puzzled. The bug is almost certainly related to commit
211b137ef46d04b17b46f256696eb5c1c3a1d2be which changed org-agenda-skip
to check text properties rather than # explicitly. I can attest that
the bug does not show with a version earlier than that commit.

OTOH, it does not show *consistently* with the most recent version.
In a minimal test, I have the following file as the only file in the
agenda list:

--8<---------------cut here---------------start------------->8---
# timestamp: <2013-01-24 Thu>

* TODO foo
  SCHEDULED: <2013-01-24 Thu>
  
--8<---------------cut here---------------end--------------->8---

and when I construct the agenda, I get the no-heading message; but if I
visit the file, and M-x describe-text-properties RET on the # in the
first line, it correctly says that the face is font-lock-comment-face;
constructing the agenda after that does *not* produce the message.

Are text properties assigned lazily perhaps? If so, they will need to be
somehow forced in this case.

Nick

PS. BTW, can you reproduce this behavior or am I tilting at windmills?