From unknown Tue Jun 17 21:52:31 2025 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 From: bug#50216 <50216@debbugs.gnu.org> To: bug#50216 <50216@debbugs.gnu.org> Subject: Status: 27.2; timeclock gives incorrect time in mode-line Reply-To: bug#50216 <50216@debbugs.gnu.org> Date: Wed, 18 Jun 2025 04:52:31 +0000 retitle 50216 27.2; timeclock gives incorrect time in mode-line reassign 50216 emacs submitter 50216 Colin Baxter severity 50216 normal thanks From debbugs-submit-bounces@debbugs.gnu.org Thu Aug 26 15:11:53 2021 Received: (at submit) by debbugs.gnu.org; 26 Aug 2021 19:11:53 +0000 Received: from localhost ([127.0.0.1]:50510 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJKn3-00082U-4D for submit@debbugs.gnu.org; Thu, 26 Aug 2021 15:11:53 -0400 Received: from lists.gnu.org ([209.51.188.17]:48284) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJKn1-00082M-25 for submit@debbugs.gnu.org; Thu, 26 Aug 2021 15:11:51 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:42160) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJKn0-0006gi-Ph for bug-gnu-emacs@gnu.org; Thu, 26 Aug 2021 15:11:50 -0400 Received: from forward108p.mail.yandex.net ([77.88.28.116]:58842) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJKmw-0001kz-SB for bug-gnu-emacs@gnu.org; Thu, 26 Aug 2021 15:11:50 -0400 Received: from myt4-5dd3963c4bb1.qloud-c.yandex.net (myt4-5dd3963c4bb1.qloud-c.yandex.net [IPv6:2a02:6b8:c12:525:0:640:5dd3:963c]) by forward108p.mail.yandex.net (Yandex) with ESMTP id A4607267EE61 for ; Thu, 26 Aug 2021 22:11:42 +0300 (MSK) Received: from myt5-ca5ec8faf378.qloud-c.yandex.net (myt5-ca5ec8faf378.qloud-c.yandex.net [2a02:6b8:c12:2514:0:640:ca5e:c8fa]) by myt4-5dd3963c4bb1.qloud-c.yandex.net (mxback/Yandex) with ESMTP id 9M4s9hG4is-BgIGAELa; Thu, 26 Aug 2021 22:11:42 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1630005102; bh=AMb/abB7TvHncV5i/VkQvvldJ8mwa2fz9dG9BBDRqUQ=; h=Subject:To:From:Message-Id:Date; b=Pm7GvPQv7BBPCN2YbZ33Pb4VkBv3ilTCdmrZRIbNgXF7N3Rz9UUg+NdOEmgSfmfnf w/X3n4XO7Mny7RnpUgy+ckDK4d7q7ODasnB2uJ626oGi7RkjZVdh5hxQ1Nj30NtXmy q0yzGDQs2apmST8rfzL6E2kIUZalXA+YzDantFKc= Authentication-Results: myt4-5dd3963c4bb1.qloud-c.yandex.net; dkim=pass header.i=@yandex.com Received: by myt5-ca5ec8faf378.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id 3j7oFaLls2-Bf2WDumW; Thu, 26 Aug 2021 22:11:41 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Date: Thu, 26 Aug 2021 20:11:40 +0100 Message-Id: <874kbcvx5f.fsf@yandex.com> From: Colin Baxter To: bug-gnu-emacs@gnu.org Subject: 27.2; timeclock gives incorrect time in mode-line MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Received-SPF: pass client-ip=77.88.28.116; envelope-from=m43cap@yandex.com; helo=forward108p.mail.yandex.net X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.3 (--) Using emacs-28.0.50: A. First Process 1. No timeclock log file 2. emacs -Q 3. In Scratch buffer, evaluate (display-time) (timeclock-mode-line-display 1) (setq timeclock-workday (* 12 60 60)) 4. mode-line reads [0:00] 5. M-x timeclock-in 6. mode-line reads [11:59] 7. Wait a minute or two. 8. M-x timeclock-out 9. mode-line reads [11:58] 10. Wrote /home/redknight/.emacs.d/timelog 11. Close emacs. Emacs correctly counts down the set workday of 12:00 hours. B. Repeat the process. 1. timeclock log file present 2. emacs -Q 3. In Scratch buffer, evaluate (display-time) (timeclock-mode-line-display 1) (setq timeclock-workday (* 12 60 60)) 4. mode-line reads [7:58] 5. Mx timeclock-in 6. mode-line reads <7:57> 7. Wrote /home/redknight/.emacs.d/timelog 8. Wait a minute or two. 9. M-x timeclock-out 10. mode-line reads [7:55] 11. Wrote /home/redknight/.emacs.d/timelog 12. Close emacs Emacs incorrectly counts down workday, starting form the default value of 8 hours even though it was set to 12 hours. C. Repeat process but change order of lisp 1. timeclock log file present 2. emacs -Q 3. In Scratch buffer, evaluate (display-time) (setq timeclock-workday (* 12 60 60)) (timeclock-mode-line-display 1) 4. mode-line reads [11:55] 5. Mx timeclock-in 6. mode-line reads <11:55> 7. Wrote /home/redknight/.emacs.d/timelog 8. Wait a minute or two. 9. M-x timeclock-out 10. mode-line reads [11:54] 11. Wrote /home/redknight/.emacs.d/timelog 12. Close emacs By setting workday before mode-line-display, Emacs gives the correct workday, counting down from the set 12 hours. D. Repeat first process A. but omit (display-time) 1. No timeclock log file 2. emacs -Q 3. In Scratch buffer, evaluate (timeclock-mode-line-display 1) Message: "Activate ‘display-time-mode’ or turn off ‘timeclock-use-display-time’ to see timeclock information" (setq timeclock-workday (* 12 60 60)) 4. M-x timeclock-in 5. mode-line reads [11:59] 6. Wait a minute or two. 7. M-x timeclock-out 8. mode-line reads [11:56] 9. Wrote /home/redknight/.emacs.d/timelog 10. Close emacs. Emacs gives the correct workday. E. Repeat process but change the lisp order 1. No timeclock log file 2. emacs -Q 3. In Scratch buffer, evaluate (setq timeclock-workday (* 12 60 60)) (timeclock-mode-line-display 1) Message: "Activate ‘display-time-mode’ or turn off ‘timeclock-use-display-time’ to see timeclock information" 4. M-x timeclock-in 5. mode-line reads [11:56] 6. Wait a minute or two. 7. M-x timeclock-out 8. mode-line reads [11:54] 9. Wrote /home/redknight/.emacs.d/timelog 10. Close emacs. Emacs again gives the correct workday even when the mode-line display occurs after the workday setting. The issue seem to be the presence or otherwise of (display-time). If it is present then the display of the set workday of 12 hours depends on when timeclock-mode-line is activated. Only if it is activated after setting the workday does the mode-line display correctly. However, if (display-time) is not used then the user gets an "Activate" message. In GNU Emacs 27.2 (build 1, i686-pc-linux-gnu, X toolkit, cairo version 1.14.8, Xaw3d scroll bars) of 2021-03-28 built on bluestar Windowing system distributor 'The X.Org Foundation', version 11.0.11902000 System Description: Debian GNU/Linux 9 (stretch) From debbugs-submit-bounces@debbugs.gnu.org Thu Aug 26 21:01:27 2021 Received: (at 50216) by debbugs.gnu.org; 27 Aug 2021 01:01:27 +0000 Received: from localhost ([127.0.0.1]:50808 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJQFL-0006JQ-8r for submit@debbugs.gnu.org; Thu, 26 Aug 2021 21:01:27 -0400 Received: from quimby.gnus.org ([95.216.78.240]:53314) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJQFI-0006JC-Qp for 50216@debbugs.gnu.org; Thu, 26 Aug 2021 21:01:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=h+khPzLeZXC+MLgMjr7dygy37q5F3+ervXkZbXfyp/k=; b=HhLkTFDfAsMfLP1OTnGYCCWIvm Apofk20w1Kq9ftUQstyKstfZbJibCiDcyZfReOwNdTrqZqRDXBaoLkOWTweT5lPN2mqVTpSjgbjyv PiQ85haV8rmwJbFAiczod8RQW5xDcm0orMnQN0nxaiUdK6jJ5zXeu+OTIElJSDLGGZp8=; Received: from [84.212.220.105] (helo=elva) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mJQF8-0008Jo-Gn; Fri, 27 Aug 2021 03:01:18 +0200 From: Lars Ingebrigtsen To: Colin Baxter Subject: Re: bug#50216: 27.2; timeclock gives incorrect time in mode-line References: <874kbcvx5f.fsf@yandex.com> Date: Fri, 27 Aug 2021 03:01:13 +0200 In-Reply-To: <874kbcvx5f.fsf@yandex.com> (Colin Baxter's message of "Thu, 26 Aug 2021 20:11:40 +0100") Message-ID: <877dg7u2ee.fsf@gnus.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Colin Baxter writes: > B. Repeat the process. > > 1. timeclock log file present > 2. emacs -Q > 3. In Scratch buffer, evaluate > (display-time) > (timeclock-mode-line-display 1) > (setq timeclock-workday (* 12 60 60)) > 4 [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 50216 Cc: 50216@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) Colin Baxter writes: > B. Repeat the process. > > 1. timeclock log file present > 2. emacs -Q > 3. In Scratch buffer, evaluate > (display-time) > (timeclock-mode-line-display 1) > (setq timeclock-workday (* 12 60 60)) > 4. mode-line reads [7:58] > 5. Mx timeclock-in > 6. mode-line reads <7:57> > 7. Wrote /home/redknight/.emacs.d/timelog > 8. Wait a minute or two. > 9. M-x timeclock-out > 10. mode-line reads [7:55] > 11. Wrote /home/redknight/.emacs.d/timelog > 12. Close emacs > > Emacs incorrectly counts down workday, starting form the default value of= 8 hours even though it was set to 12 hours. Thanks for the detailed recipes. I tried this in Emacs 28, and I can reproduce the problem. However, I'm seeing exactly the same behaviour in Emacs 27.2 (and earlier), and I think you said over on emacs-devel that this used to work there? > E. Repeat process but change the lisp order > > 1. No timeclock log file > 2. emacs -Q > 3. In Scratch buffer, evaluate > (setq timeclock-workday (* 12 60 60)) > (timeclock-mode-line-display 1) > Message: "Activate =E2=80=98display-time-mode=E2=80=99 or turn off =E2= =80=98timeclock-use-display-time=E2=80=99 to see timeclock information" > 4. M-x timeclock-in > 5. mode-line reads [11:56] > 6. Wait a minute or two. > 7. M-x timeclock-out > 8. mode-line reads [11:54] > 9. Wrote /home/redknight/.emacs.d/timelog > 10. Close emacs. > > Emacs again gives the correct workday even when the mode-line display > occurs after the workday setting. > > The issue seem to be the presence or otherwise of (display-time). I'm not so sure. In all the cases where things work correctly (when setting timeclock after `timeclock-mode-line-display'), there's no timelog file. So the issue seems to be: Setting workday after timeclock + having a log file? I haven't really started debugging in, but the issue seems to be `timeclock-find-discrep' using some data that was computed before timeclock-workday was set... --=20 (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no From debbugs-submit-bounces@debbugs.gnu.org Thu Aug 26 21:13:52 2021 Received: (at 50216) by debbugs.gnu.org; 27 Aug 2021 01:13:52 +0000 Received: from localhost ([127.0.0.1]:50812 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJQRI-0006Zq-Fg for submit@debbugs.gnu.org; Thu, 26 Aug 2021 21:13:52 -0400 Received: from quimby.gnus.org ([95.216.78.240]:53470) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJQRD-0006ZY-EU for 50216@debbugs.gnu.org; Thu, 26 Aug 2021 21:13:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=dNEfUW+F/mcIQ2Ka3nGrvMGbpQkY/8ZygLsoql+Tobc=; b=HVxAv2MNOZUz7hmVxM6xISEye5 CTC+V0PMLny5ty8qRd82ZW1n+079cupyv0xcgE7PC7LG9GHzbe9TyIzaHWGgHPEqXHbTPnHsfSJQe YPF7JcCYafwbNCQzLUge6HXyt3tbUVQu/5pJLZ/CSNNrlnmAGTFCcBsXRhjZKos6zl/E=; Received: from [84.212.220.105] (helo=elva) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mJQR2-0008SK-SJ; Fri, 27 Aug 2021 03:13:37 +0200 From: Lars Ingebrigtsen To: Colin Baxter Subject: Re: bug#50216: 27.2; timeclock gives incorrect time in mode-line References: <874kbcvx5f.fsf@yandex.com> <877dg7u2ee.fsf@gnus.org> Date: Fri, 27 Aug 2021 03:13:32 +0200 In-Reply-To: <877dg7u2ee.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 27 Aug 2021 03:01:13 +0200") Message-ID: <8735qvu1tv.fsf@gnus.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Lars Ingebrigtsen writes: > I haven't really started debugging in, but the issue seems to be > `timeclock-find-discrep' using some data that was computed before > timeclock-workday was set... Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 50216 Cc: 50216@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) Lars Ingebrigtsen writes: > I haven't really started debugging in, but the issue seems to be > `timeclock-find-discrep' using some data that was computed before > timeclock-workday was set... Yup, that was it -- I made it flush the data on workday changes, and now it displays correctly for me in the timelog test case -- that is, when doing timelog-in, it'll use the current timelog-workday setting and compute stuff correctly. Note, however, that initial display when doing (timeclock-mode-line-display 1) (setq timeclock-workday (* 12 60 60)) will be incorrect -- because setting a variable like this won't trigger mode-line updates. (Until a minute has passed and it updates the line.) So I've noted in the timeclock-mode-line-display doc string that this shouldn't be done. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no From debbugs-submit-bounces@debbugs.gnu.org Thu Aug 26 21:13:57 2021 Received: (at control) by debbugs.gnu.org; 27 Aug 2021 01:13:57 +0000 Received: from localhost ([127.0.0.1]:50815 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJQRN-0006a7-Q5 for submit@debbugs.gnu.org; Thu, 26 Aug 2021 21:13:57 -0400 Received: from quimby.gnus.org ([95.216.78.240]:53484) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJQRI-0006Ze-EN for control@debbugs.gnu.org; Thu, 26 Aug 2021 21:13:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Subject:From:To:Message-Id:Date:Sender:Reply-To:Cc: MIME-Version:Content-Type:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=G65N5pe9ffp25/L/Yqiw4Y1zpB9kTrPtcyiQClNgZ/w=; b=Gs6ndoI5AGYvRhALJELH7lXlc/ UCNN9YOsMPtbGIrpyYW9b9NTTmyjFKE25KPwT2PVrynYj2OXVWgAgU1pzaYMpqxPeIWC5QOppTGEX cCdyCapkZFYe88aG4pymFVI6thm/IekaZxH5LiaRiLf5BqRfrDiCkuimPikkvUrZINqg=; Received: from [84.212.220.105] (helo=elva) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mJQRA-0008SU-L6 for control@debbugs.gnu.org; Fri, 27 Aug 2021 03:13:42 +0200 Date: Fri, 27 Aug 2021 03:13:40 +0200 Message-Id: <871r6fu1tn.fsf@gnus.org> To: control@debbugs.gnu.org From: Lars Ingebrigtsen Subject: control message for bug #50216 X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: close 50216 28.1 quit Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: control X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) close 50216 28.1 quit From debbugs-submit-bounces@debbugs.gnu.org Fri Aug 27 02:53:15 2021 Received: (at 50216) by debbugs.gnu.org; 27 Aug 2021 06:53:15 +0000 Received: from localhost ([127.0.0.1]:51148 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJVjm-0004mu-Qf for submit@debbugs.gnu.org; Fri, 27 Aug 2021 02:53:15 -0400 Received: from forward104o.mail.yandex.net ([37.140.190.179]:53962) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJVjk-0004me-MQ for 50216@debbugs.gnu.org; Fri, 27 Aug 2021 02:53:14 -0400 Received: from sas2-5b46325ecb6a.qloud-c.yandex.net (sas2-5b46325ecb6a.qloud-c.yandex.net [IPv6:2a02:6b8:c14:251e:0:640:5b46:325e]) by forward104o.mail.yandex.net (Yandex) with ESMTP id D6EF265D771C; Fri, 27 Aug 2021 09:53:04 +0300 (MSK) Received: from sas8-b61c542d7279.qloud-c.yandex.net (sas8-b61c542d7279.qloud-c.yandex.net [2a02:6b8:c1b:2912:0:640:b61c:542d]) by sas2-5b46325ecb6a.qloud-c.yandex.net (mxback/Yandex) with ESMTP id IgliD6EjzQ-r4HC1b4v; Fri, 27 Aug 2021 09:53:04 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1630047184; bh=NqUM2ZvY6j6cTfDIJBaDcBXdt25GJp04XxKXjWGFpzI=; h=In-Reply-To:Subject:Date:References:To:From:Message-ID:Cc:Cc; b=MZffGTZAzHphlg4IDp2JKnuuOybkobQl/sNfqJFT0eCwn0W/0Zf9bJEDaLoQSmZJU LJnB1/z8q53y5ayoVWW4tCCP1d47L+1RlzH3tRxTs3ey0+962P8iQtlHfdAvH02JUE BjelBFjSqbR5m+mhKE4C9LQ2Dd9hKjr1yBPBdNJk= Authentication-Results: sas2-5b46325ecb6a.qloud-c.yandex.net; dkim=pass header.i=@yandex.com Received: by sas8-b61c542d7279.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id 5F1WU5r3nQ-r3baHinF; Fri, 27 Aug 2021 09:53:03 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) From: Colin Baxter To: Lars Ingebrigtsen Subject: Re: bug#50216: 27.2; timeclock gives incorrect time in mode-line References: <874kbcvx5f.fsf@yandex.com> <877dg7u2ee.fsf@gnus.org> <8735qvu1tv.fsf@gnus.org> X-Face: BHjiJOg/Qmj'BQgsAKL@])L)e62P)C"Y=6T Date: Fri, 27 Aug 2021 07:53:02 +0100 In-Reply-To: <8735qvu1tv.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 27 Aug 2021 03:13:32 +0200") Message-ID: <87czpzl6pd.fsf@yandex.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Face: iVBORw0KGgoAAAANSUhEUgAAAEkAAAATAgMAAAChCMjeAAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAACVBMVEX/zAABCWP///8I RHjYAAAAAWJLR0QCZgt8ZAAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB+UFEAk5BvqS634A AAAbSURBVBjTY2BgCA1hYA0FAxDDgQEERsXoIAYA2F9Eb3cpB+AAAAAldEVYdGRhdGU6Y3JlYXRl ADIwMjEtMDUtMTZUMTA6NTY6MTcrMDE6MDCh/kkpAAAAJXRFWHRkYXRlOm1vZGlmeQAyMDIxLTA1 LTE2VDA5OjU3OjA2KzAxOjAwTyZ6HwAAAABJRU5ErkJggg== MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 50216 Cc: , 50216@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) >>>>> Lars Ingebrigtsen writes: > Lars Ingebrigtsen writes: >> I haven't really started debugging in, but the issue seems to be >> `timeclock-find-discrep' using some data that was computed before >> timeclock-workday was set... > Yup, that was it -- I made it flush the data on workday changes, > and now it displays correctly for me in the timelog test case -- > that is, when doing timelog-in, it'll use the current > timelog-workday setting and compute stuff correctly. > Note, however, that initial display when doing > (timeclock-mode-line-display 1) (setq timeclock-workday (* 12 60 > 60)) > will be incorrect -- because setting a variable like this won't > trigger mode-line updates. (Until a minute has passed and it > updates the line.) So I've noted in the > timeclock-mode-line-display doc string that this shouldn't be > done. Thank you very much. I think I am *beginning* to understand what's happening. I was wrong about it only being an emacs-28 issue. As you wrote in an earlier email, you can see the same effect in emacs-27. Best wishes, From unknown Tue Jun 17 21:52:31 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Fri, 24 Sep 2021 11:24:05 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator