Re: org-today broken

[Marco Wahl <marcowahlsoft@gmail.com>]

Hi Kyle,

>> Occasionally I like to bend time to see what the agenda would look like
>> if another day was current.  This can be achieved conveniently when
>> solely function "current-time" is the source for the current time.
>>
>> So I'm all for using the explicit calls to current-time instead of using
>> alternatve sources for the current time.
>
> Sorry for making your time travel harder :]

:[

> Emacs's c75f505dea6 argues for replacing current-time calls with nil
> where possible because "nil is a bit more efficient and should have less
> timing error".  But if there are any particular spots where you'd like
> to use current-time for the reasons you give above, please feel free to
> make those changes.  (There are already quite a few places where I've
> done this because we depend on overriding current-time in tests.)

Thanks for the clarification.

I think it's a not so great idea to build on an assumption about some
internal stuff, here concretely the expectation that the current time is
retrieved per call to `current-time' everywhere in Org.

If there shall be a time travel feature in Org this feature should be
made explicit, I think, which BTW could be ensured with suitable tests.

Possibly one could use external tools to get even more powerful
timetravel, as Marcin proposed IIRC.

So go ahead with every optimization you can find!


Best regards,  Marco