From: Daniel Ortmann <dortmann31415@pobox.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] org agenda showing current time - not task time when closing repeatedly-scheduled task [9.7-pre (release_9.6.10-840-g9fcbd1 @ /home/d/src/git-org-mode/lisp/)]
Date: Mon, 16 Oct 2023 15:50:11 -0500 [thread overview]
Message-ID: <d9b1cc84-7140-4999-82c6-5fd186aef0fd@pobox.com> (raw)
In-Reply-To: <87fs2b9fv9.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
A bit more clarity ...
* If the task clock is activated on a TODO in the agenda,
* and closed quickly enough that the elapsed time is 0:00,
* then MOMENTARILY the agenda shows the CURRENT WALLCLOCK TIME.
* The actual logbook entry shows the correct 0:00 elapsed task time.
* And when the agenda is merely REFRESHED the wallclock time is
replaced with the 0:00.
So there seems to be NO BUG. It's just an odd transient behavior which
I now noticed only because of tracking "time" on some small tasks.
Definitely not worth touching brittle code. "It's just how it is."
And that's ok! :-)
Thank you for your attention to this matter which now is clearly smaller
than expected.
On 10/16/23 02:38, Ihor Radchenko wrote:
> Daniel Ortmann<dortmann31415@pobox.com> writes:
>
>> No, no, not clock check mode.
>>
>> - I created a TODO with a scheduled time that repeats. When completed
>> it remains alive to be scheduled the next day.
>>
>> - I started the clock on that TODO task.
>>
>> - Then completed the task with 't' in the Agenda view.
>>
>> - The task's "clock time" shows in the log ... i.e. how much time I
>> spent completing that task.
> Ok. Got it.
>
>> ==>> Previously, a day or so ago, the current local time was recorded in
>> the Agenda log rather than the "clock time" (i.e. rather than the time
>> spent to complete the task).
>>
>> ==>> Now, the current "clock time" again is correctly recorded in the log.
> I looked into the code, and I do have a feeling that it is brittle
> (agenda is a very old and convoluted code), but without a concrete
> reproducer I wouldn't dare to touch it.
>
>> I hope the screen captured images came across in the previous email?
>> They should help explain.
> I indeed did not notice the attachments - they were not indicated in the
> plain/text part of the email. They indeed did help to explain things.
>
[-- Attachment #2: Type: text/html, Size: 2966 bytes --]
prev parent reply other threads:[~2023-10-16 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 14:56 [BUG] org agenda showing current time - not task time when closing repeatedly-scheduled task [9.7-pre (release_9.6.10-840-g9fcbd1 @ /home/d/src/git-org-mode/lisp/)] Daniel Ortmann
2023-10-15 8:39 ` Ihor Radchenko
2023-10-15 8:52 ` Daniel Ortmann
2023-10-15 9:00 ` Ihor Radchenko
2023-10-15 9:13 ` Daniel Ortmann
2023-10-16 7:38 ` Ihor Radchenko
2023-10-16 20:50 ` Daniel Ortmann [this message]
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=d9b1cc84-7140-4999-82c6-5fd186aef0fd@pobox.com \
--to=dortmann31415@pobox.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).