From: Tebe Nigrelli <nigrellitebe@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] - org-agenda log view does not conform to org-timestamp-formats
Date: Wed, 27 Dec 2023 22:56:23 +0100 [thread overview]
Message-ID: <c0936832-c579-4c04-85ba-69bb8ec74183@gmail.com> (raw)
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.
next reply other threads:[~2023-12-27 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 21:56 Tebe Nigrelli [this message]
2023-12-28 11:37 ` [BUG] - org-agenda log view does not conform to org-timestamp-formats Ihor Radchenko
[not found] ` <13a90e1b-2f48-4c1b-8720-f21804b5c950@gmail.com>
2023-12-28 12:43 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0936832-c579-4c04-85ba-69bb8ec74183@gmail.com \
--to=nigrellitebe@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).