Hello,
Matt Lundin writes:
> Attached please find a patch that fixes these issues. It is a simple
> change, but it brings the behavior of %^t and %^u vs. %^T and %^U into
> line with the behavior of the interactive function org-time-stamp
> without and with a prefix argument.
>
> The escapes %^t
Matt Lundin writes:
> Matt Lundin writes:
>
>> After commit 51b431d01365211d4c40b07729d5d11d82b9dfe2,
>> org-capture-templates containing %^t do not work as expected.
>>
>> With this capture template, I am prompted to enter a time via
>> org-read-date. The expected behavior is as follows:
>>
>>
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") "* %^{App
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")))
W
