Michaël Cadilhac writes:
> Thanks for your expertise Adam.
Glad I could help, but I think you did the sleuthing here. ;)
> It seems indeed that org-agenda-capture (or equivalently, setting
> org-capture-use-agenda-date) affects the default date at all stages,
> i.e., for %u and for the defau
On 5 August 2017 at 04:27, Adam Porter wrote:
> Michaël Cadilhac writes:
>
>> However, suppose I'm in Calfw; I jump to some date, hit SPACE and I'm
>> now in Org-Agenda mode, ready to hit k to capture (because Calfw-Org
>> does not offer this directly). Now I expect %U to still be the
>> current
Michaël Cadilhac writes:
> However, suppose I'm in Calfw; I jump to some date, hit SPACE and I'm
> now in Org-Agenda mode, ready to hit k to capture (because Calfw-Org
> does not offer this directly). Now I expect %U to still be the
> current time stamp, and %^t to be prefilled with the date of
Hi there people;
I have a few TODO templates of the form:
("td" "Todo deadline (with reminders)" entry
(file "~/org/todos.org")
"* TODO %^{Todo}\n DEADLINE: %^t\n %U\n%i%?")
The goal is to have two time stamps: an inactivated one (%U),
recording the time the TODO
