Bastien writes:
> Achim Gratz writes:
>> Probably yes, although there are other variables that should probably be
>> bound in this case (and maybe others).
>
> If you can think of some others, please let us know.
The docstring of org-minutes-to-clocksum-string says:
"Format number of minutes a
Hi Achim,
Achim Gratz writes:
> Probably yes, although there are other variables that should probably be
> bound in this case (and maybe others).
If you can think of some others, please let us know.
Thanks,
--
Bastien
Hi Vincent,
Vincent Beffara writes:
> I am afraid to change the code, so I just customized
Com'on, don't be afraid!
> org-time-clocksum-use-effort-durations to nil and everything works for
> now. But presumably this should be fixed by letting it be nil while
> formatting the end timestamp, som
Vincent Beffara writes:
> I am afraid to change the code, so I just customized
> org-time-clocksum-use-effort-durations to nil and everything works for
> now. But presumably this should be fixed by letting it be nil while
> formatting the end timestamp, somewhere near line 6404 of
> org-agenda.el ?
Ha, I got it !
When displaying the end time of an interval in agenda view, org-agenda
transforms the initial time stamp to minutes, adds the default length to that
and maps back to a time stamp using org-minutes-to-clocksum-string. The problem
being that this functions checks org-time-clocksum
