From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Date-stamps w/o time are shown with time on agenda Date: Wed, 13 Nov 2013 15:28:10 +0100 Message-ID: <878uwss7et.fsf@bzg.ath.cx> References: <2013-11-13T13-52-57@devnull.Karl-Voit.at> <87siv02yqn.fsf@bzg.ath.cx> <2013-11-13T14-57-52@devnull.Karl-Voit.at> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49087) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VgbQZ-0000E5-Ji for emacs-orgmode@gnu.org; Wed, 13 Nov 2013 09:28:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VgbQU-0004e3-2E for emacs-orgmode@gnu.org; Wed, 13 Nov 2013 09:28:19 -0500 Received: from mail-wg0-x231.google.com ([2a00:1450:400c:c00::231]:45656) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VgbQT-0004cP-RU for emacs-orgmode@gnu.org; Wed, 13 Nov 2013 09:28:13 -0500 Received: by mail-wg0-f49.google.com with SMTP id x13so478448wgg.28 for ; Wed, 13 Nov 2013 06:28:13 -0800 (PST) In-Reply-To: <2013-11-13T14-57-52@devnull.Karl-Voit.at> (Karl Voit's message of "Wed, 13 Nov 2013 15:00:50 +0100") 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: Karl Voit Cc: news1142@Karl-Voit.at, emacs-orgmode@gnu.org Hi Karl, Karl Voit 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 > as whole-day items on the agenda and 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