Steps to reproduce:
Changing org-timestamp-formats to include the timezone: ("<%Y-%m-%d %a
%Z>" . "<%Y-%m-%d %a %H:%M %Z>"), a clock line will look like this:
(https://emacs.stackexchange.com/questions/13463/specify-timezone-in-org-date-format)
CLOCK: [2023-01-28 Sat 17:04 CET]--[2023-01-28 Sat 18:04 CET] => 1:00
After toggling the "log view" in the org-agenda, the clock's line does
not contain duration of the clock, instead showing "(-)" in the
duration, as ongoing / error:
Expected behaviour: "Filename: 17:04-18:04 ┄┄┄┄┄ Clocked: (1:00)
Activity"
Shown behaviour: "Filename: 17:04 ┄┄┄┄┄ Clocked: (-) Activity"
Relevant:
Writing a duration ("%H:%M") at the 59th character of the clock
line (where the duration would have been if the timestamps had normal
length) results in the agenda reading the number and placing it in the
parenthesis, suggesting that a fixed number of characters is skipped
before reading the duration of the clock, for efficiency.
org-clock-report works as intended, so does org-ctrl-c-ctrl-c (fixing
the date, writing the duration at the end of the line). The issue seems
limited to the agenda.
Could be related to org-agenda-get-progress, but I am not sure.
