From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: Bug: org-capture-templates with %^t Date: Thu, 05 Oct 2017 09:43:08 -0500 Message-ID: <87bmlllkpz.fsf@fastmail.fm> References: <87h8vfj0bo.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43262) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e07Mq-0007no-QZ for emacs-orgmode@gnu.org; Thu, 05 Oct 2017 10:43:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e07Mn-0001J1-M6 for emacs-orgmode@gnu.org; Thu, 05 Oct 2017 10:43:16 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:59949) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1e07Mn-0001Hh-Fj for emacs-orgmode@gnu.org; Thu, 05 Oct 2017 10:43:13 -0400 Received: from archdesk (wcnat-96-20.wheaton.edu [209.147.96.20]) by mail.messagingengine.com (Postfix) with ESMTPA id B050924009 for ; Thu, 5 Oct 2017 10:43:09 -0400 (EDT) In-Reply-To: <87h8vfj0bo.fsf@fastmail.fm> (Matt Lundin's message of "Tue, 03 Oct 2017 18:21:16 -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" To: Org Mode Matt Lundin writes: > After commit 51b431d01365211d4c40b07729d5d11d82b9dfe2, > org-capture-templates containing %^t do not work as expected. > > The relevant capture template snippet looks like this: > > (setq org-capture-templates > '(("a" "Appointment" entry (file "~/inbox.org") "* %^{Appt}\n %^t%?\n %U\n > %a\n\n %i"))) > > With this capture template, I am prompted to enter a time via > org-read-date. The expected behavior is as follows: > > - if I enter a date and time of day, the resulting timestamp should > contain the time of day: > - i.e., entering "Thu 8am" should yield "<2017-10-05 Thu 08:00>" > > What happens now: > > - when I enter a date with a time of day, the timestamp is truncated > and contains only a date > - I.e., entering "Thu 8am" now yields "<2017-10-05 Thu>" > There is a further bug here. With the capture template above, if I enter a time range - i.e., an end time - the timestamp in the capture buffer is incorrect. Entering... "Thu 8am-10am" yields... <2017-10-05 Thu-10:00> Best, Matt