From: Ihor Radchenko <yantar92@posteo.net>
To: Daniel Ortmann <dortmann31415@pobox.com>
Cc: 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: Sun, 15 Oct 2023 09:00:55 +0000 [thread overview]
Message-ID: <87pm1g9s54.fsf@localhost> (raw)
In-Reply-To: <98b54a6e-d232-4267-b350-187f37ee2675@pobox.com>
Daniel Ortmann <dortmann31415@pobox.com> writes:
> In the last entry below, the "Clocked:" part of the log would have
> showed 3:47 (i.e. the current local CDT time) rather than the time to
> complete the task which is now correctly shown as 0:01 minutes.
Do you mean that you used agenda clockcheck mode? I tried and I see no
problem there.
> The problem no longer appears! Excellent. Not sure what fixed it.
> ...
> Problem fixed ... but it would be nice to know it was not an accidental fix.
I am not sure what you mean by fixed. Did you do anything?
> Thank you! You can close it or investigate further at your discretion.
I am not able to reproduce the problem. Since you cannot either, I am
closing this bug.
Canceled.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-10-15 9:00 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 [this message]
2023-10-15 9:13 ` Daniel Ortmann
2023-10-16 7:38 ` Ihor Radchenko
2023-10-16 20:50 ` Daniel Ortmann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pm1g9s54.fsf@localhost \
--to=yantar92@posteo.net \
--cc=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.