From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id 0AAJF3ijLWUKpQAAG6o9tA:P1 (envelope-from ) for ; Mon, 16 Oct 2023 22:56:24 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id 0AAJF3ijLWUKpQAAG6o9tA (envelope-from ) for ; Mon, 16 Oct 2023 22:56:24 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 59BB465C74 for ; Mon, 16 Oct 2023 22:56:23 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=pobox.com header.s=sasl header.b="ozSZD/ZO"; dmarc=pass (policy=none) header.from=pobox.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1697489784; a=rsa-sha256; cv=none; b=XbZ1s1VgFRrY+uD4flX9uhz1P6TqKS1H02HKaPNP7qXe/0fKElZak/AidvL+SZqdbovhZC OSN6xphzHMHj4jeqYCv1CiJO350AUvVIucwXG47s5Tvfze5rxHlOoeKHljgCOO2n6lbPVr v7sGxl5rfHwciz6XBUw14CiWZwkVqviw+heK083tY4ca+Xn2wU5ph9j6GD7rDqkrkgJbi/ ejhoe68V1H0SsPOtVxpc4gBvi2vESltUwHcNVJ+cbCkNjc8EUiaK6L/A6zigUwDYAGDPdA kAjv5Zn/3wQxbXgTNnMrSCRVAl92i3e1B+UXViESlS8iOm812H3u5q8lJyxBwQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=pobox.com header.s=sasl header.b="ozSZD/ZO"; dmarc=pass (policy=none) header.from=pobox.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1697489784; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=x2q1BxV8my0YFG+an8L3h+jYs0/1Rl8nu7OQdKtuZeM=; b=Q5XYKdUKWAHyhyZO4y4ZF/Mb3hgV6SDlo+9pPZiO9f5jYD0XXmyPaUnyMd0ZX6N7DSWBF8 qszAb2l9QH9+edGaFsXIk1cDsazajYQi/mQxE6qIqawtusGtlO8/690Iyto9/r6ft3CR3S 8jYnpFnqFNQ4muyTcnaQ/JuksQOtnCyuGf9KccANhsaq6Na7Za/iAzMBC9rAxB0NY7l86A fEL+FvIh+u+vIgN5PHTvevXBEDf/51oyEcSOiSdJx2ZbBHcaOSBSdUBmKco8WvjVSgx4ga RTgsEAUGlZh0gmFKd6YsNa1Yi8GKgRvVRsoJOHHCJD+wumu+uMnxt2wvXe/qeA== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qsUXd-0005zW-95; Mon, 16 Oct 2023 16:50:21 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qsUXb-0005zE-Qz for emacs-orgmode@gnu.org; Mon, 16 Oct 2023 16:50:19 -0400 Received: from pb-smtp1.pobox.com ([64.147.108.70]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qsUXa-0004AY-2c for emacs-orgmode@gnu.org; Mon, 16 Oct 2023 16:50:19 -0400 Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id E35311AE1A0 for ; Mon, 16 Oct 2023 16:50:13 -0400 (EDT) (envelope-from dortmann31415@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h= content-type:message-id:date:mime-version:subject:to:references :from:in-reply-to; s=sasl; bh=9pUY1kcRBzdqDGFgwL8HA6ykugkcyEt1t9 MfGdCsjM8=; b=ozSZD/ZOADwVoLu/Hcj0t1l1BJ3UpsKwu+1O2IrGjxf18vNokP Ja0i+EYJ26SI9cCG+Q7NMjUbqTrLxh5ZKAm5CsdDNBwJhmT/VObOBBvoNJmRqd2y JQe+gkqe5FgJ3s3PsXNPyH8b27o++j1aQjFGzCH4oLRoxLkuiCzSklULA= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id DAECE1AE19F for ; Mon, 16 Oct 2023 16:50:13 -0400 (EDT) (envelope-from dortmann31415@pobox.com) Received: from [10.0.0.22] (unknown [76.17.243.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 23D6D1AE19E for ; Mon, 16 Oct 2023 16:50:13 -0400 (EDT) (envelope-from dortmann31415@pobox.com) Content-Type: multipart/alternative; boundary="------------KDxXMVq8VWgs0AdiiGlHzjLX" Message-ID: Date: Mon, 16 Oct 2023 15:50:11 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird 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/)] Content-Language: en-US To: emacs-orgmode@gnu.org References: <87y1g49t49.fsf@localhost> <98b54a6e-d232-4267-b350-187f37ee2675@pobox.com> <87pm1g9s54.fsf@localhost> <87fs2b9fv9.fsf@localhost> From: Daniel Ortmann In-Reply-To: <87fs2b9fv9.fsf@localhost> X-Pobox-Relay-ID: 9A619DD6-6C65-11EE-BB2E-78DCEB2EC81B-67203687!pb-smtp1.pobox.com Received-SPF: pass client-ip=64.147.108.70; envelope-from=dortmann31415@pobox.com; helo=pb-smtp1.pobox.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx1.migadu.com X-Migadu-Spam-Score: -7.94 X-Spam-Score: -7.94 X-Migadu-Queue-Id: 59BB465C74 X-TUID: 3dqwd8Qafml3 This is a multi-part message in MIME format. --------------KDxXMVq8VWgs0AdiiGlHzjLX Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable 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.=C2=A0 It's just an odd transient behavior wh= ich=20 I now noticed only because of tracking "time" on some small tasks. Definitely not worth touching brittle code.=C2=A0 "It's just how it is." And that's ok!=C2=A0 :-) Thank you for your attention to this matter which now is clearly smaller=20 than expected. On 10/16/23 02:38, Ihor Radchenko wrote: > Daniel Ortmann writes: > >> No, no, not clock check mode. >> >> - I created a TODO with a scheduled time that repeats.=C2=A0 When comp= leted >> 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. > >> =3D=3D>> Previously, a day or so ago, the current local time was recor= ded in >> the Agenda log rather than the "clock time" (i.e. rather than the time >> spent to complete the task). >> >> =3D=3D>> 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 th= e > plain/text part of the email. They indeed did help to explain things. > --------------KDxXMVq8VWgs0AdiiGlHzjLX Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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.=C2=A0 It's just an odd transient behavio= r which I now noticed only because of tracking "time" on some small tasks.

Definitely not worth touching brittle code.=C2=A0 "It's just how it i= s."

And that's ok!=C2=A0 :-)

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 <dortman=
n31415@pobox.com> writes:


No, no, not clock check mo=
de.

- I created a TODO with a scheduled time that repeats.=C2=A0 When complet=
ed=20
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=20
spent completing that task.

Ok. Got it.


=3D=3D>> Previously,=
 a day or so ago, the current local time was recorded in=20
the Agenda log rather than the "clock time" (i.e. rather than the time=20
spent to complete the task).

=3D=3D>> 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?=C2=A0=20
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.

--------------KDxXMVq8VWgs0AdiiGlHzjLX--