agzam.ibragi...@gmail.com writes: > 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 org-popup-calendar-for-date-prompt nil) > (read-date t))) > > And again, type some time value in the prompt - it returns date with no > time. This seems to be a bug.
I can confirm this behavior with org-read-date instead of read-date. And at first glance I also think this is a bug. I capture this issue for someday. But of course anyone please feel free to fix this. The same holds for the idea to add "h" (hours) and possibly "M" (minutes) as a further way to specify the hour via org-read-date. Thanks!