Bastien writes:
> Tom writes:
>
>> It is a consistency bug then. If thu 8am works in other cases
>> then it should not be the user's job to know which format to
>> use to achieve to desired result. Org should treat both
>> forms in the same way.
>
> Please try the attached patch and report other
Tom writes:
> It is a consistency bug then. If thu 8am works in other cases
> then it should not be the user's job to know which format to
> use to achieve to desired result. Org should treat both
> forms in the same way.
Please try the attached patch and report other inconsistencies.
Thanks,
Bastien gnu.org> writes:
>
> You need to enter 8am thu in this case.
>
It is a consistency bug then. If thu 8am works in other cases
then it should not be the user's job to know which format to
use to achieve to desired result. Org should treat both
forms in the same way.
Hi Tom,
Tom writes:
> I have
>
> (setq org-read-date-prefer-future 'time)
>
> in my .emacs, so if I give a time like 8am and it is before now
> then it is interpreted as tomorrow. This is good, because I never
> want to set times in the past.
>
> However if I give "thu 8am" (it is Thursday 11:5
I have
(setq org-read-date-prefer-future 'time)
in my .emacs, so if I give a time like 8am and it is before now
then it is interpreted as tomorrow. This is good, because I never
want to set times in the past.
However if I give "thu 8am" (it is Thursday 11:50am here, so Thu 8am
is before now) th
