From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@altern.org>
Subject: Re: [Bug] org-capture datetree+prompt: wrong time (range)
 information in timestamp (%T escape sequence)
Date: Mon, 24 Sep 2012 16:00:20 +0200
Message-ID: <87d31bo70r.fsf@bzg.ath.cx>
References: <20120923194954.GE25237@boo.workgroup>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:53071)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1TG9Cy-0007C8-Ry
	for emacs-orgmode@gnu.org; Mon, 24 Sep 2012 10:00:32 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1TG9Cs-0005vq-9P
	for emacs-orgmode@gnu.org; Mon, 24 Sep 2012 10:00:24 -0400
Received: from mail-wg0-f49.google.com ([74.125.82.49]:60889)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1TG9Cs-0005v3-1t
	for emacs-orgmode@gnu.org; Mon, 24 Sep 2012 10:00:18 -0400
Received: by wgbdt14 with SMTP id dt14so3678570wgb.30
	for <emacs-orgmode@gnu.org>; Mon, 24 Sep 2012 07:00:16 -0700 (PDT)
In-Reply-To: <20120923194954.GE25237@boo.workgroup> (Gregor Zattler's message
	of "Sun, 23 Sep 2012 21:49:54 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: emacs-orgmode <emacs-orgmode@gnu.org>

Hi Gregor,

Gregor Zattler <telegraph@gmx.net> writes:

> But there are two problems with the time information, which I
> consider to be bugs:
>
> 1) If I enter a time *range* at the prompt, the %T expands to the
>    time when I invoked the capture ("now") while the date is
>    still the entered day, not today.  This is a mixture of the
>    events date / recording time which I consider to be a bug.
>    Instead I expect to see the date and time range of the
>    appointment.

The %T specifier do not allow ranges.  I've changed the behavior 
here so that, when the user specifies a time range, only the first
time spec is taken into account.

> 2) If I do not enter a time at all, since for instance the date
>    is not bound to a time (e.g. holiday, birthday) the %T also
>    expands to the time when I invoked the capture ("now") while
>    the date is still the entered day, not today.

The %T specifier _requires_ a time to be set (otherwise you would use
%t), but I agree the current time looks wrong here.  So this is now
00:00 instead.  This does not look perfect, but it's better IMHO.

Thanks for reporting these bugs.

Best,

-- 
 Bastien