Hi Karl, Karl Voit <devn...@karl-voit.at> writes:
> I am sorry - I do not see the contradiction here. Sorry, I read too fast. > Why not handle each time-stamp in a consistent manner: show each > <YYYY-MM-DD ddd> as whole-day items on the agenda and <YYYY-MM-DD > ddd HH:MM> as items with an associated time (and duration)? (setq org-agenda-search-headline-for-time nil) should do. When Org tries to associate a headline with a timestamp found in a subtree, it optionally tries to find a time string (like "HH:MM") in the headline if this option is `t' (the default.) Here it confuses the time string from the timestamp with a separate time string, hence the confusion. -- Bastien
