Hi Marco,
Marco Wahl writes:
> In summary I can say that this LGTM and I can't reproduce the
> problem.
Thanks for taking the time and trouble to try reproducing it!
--
Bastien
Bastien writes:
> I tried
>
> (progn
> (setq org-popup-calendar-for-date-prompt t)
> (org-read-date t))
>
> (progn
> (setq org-popup-calendar-for-date-prompt nil)
> (org-read-date t))
>
> from master and could not reproduce the problem (not having the
> inserted time string taken into
Hi,
I tried
(progn
(setq org-popup-calendar-for-date-prompt t)
(org-read-date t))
(progn
(setq org-popup-calendar-for-date-prompt nil)
(org-read-date t))
from master and could not reproduce the problem (not having the
inserted time string taken into account).
Marco, can you reproduce
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
