Re: [O] Bug: org-read-date ignores hours?

2019-10-24 Thread agzam . ibragimov
While fooling around with capture templates, I have also noticed this: (progn (setq org-popup-calendar-for-date-prompt t) (read-date t))) When prompted, if you type something like "13:00" - it returns correct, expected datetime. But, if you do: (progn (setq

Re: [O] Bug: org-read-date ignores hours?

2019-10-24 Thread Marco Wahl
Hi Ag, > When I use (org-read-date t) and type something like "+2m" it works as > expected, but for > some reason if I type something like "+2h" it returns datetime with no > changes. Expected - two hours in the future. Am I missing something? AFAICS your expectation is not implemented. See

[O] Bug: org-read-date ignores hours?

2019-10-22 Thread Ag Ibragimov
When I use (org-read-date t) and type something like "+2m" it works as expected, but for some reason if I type something like "+2h" it returns datetime with no changes. Expected - two hours in the future. Am I missing something?