From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Mike Kupfer Newsgroups: gmane.emacs.devel Subject: Re: Extending timeclock.el Date: Sat, 06 May 2023 15:10:28 -0700 Message-ID: <24738.1683411028@alto> References: <83ild6gc54.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27637"; mail-complaints-to="usenet@ciao.gmane.io" Cc: John Task , emacs-devel@gnu.org, John Wiegley To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 07 00:11:32 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pvQ7o-00075n-A3 for ged-emacs-devel@m.gmane-mx.org; Sun, 07 May 2023 00:11:32 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pvQ7A-0000fr-UO; Sat, 06 May 2023 18:10:53 -0400 Original-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 1pvQ78-0000fe-NC for emacs-devel@gnu.org; Sat, 06 May 2023 18:10:50 -0400 Original-Received: from shell1.rawbw.com ([198.144.192.42]) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pvQ76-000809-Ry; Sat, 06 May 2023 18:10:50 -0400 Original-Received: from alto (135-180-173-181.dsl.dynamic.sonic.net [135.180.173.181] (may be forged)) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id 346MASCT054647 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 6 May 2023 15:10:33 -0700 (PDT) (envelope-from kupfer@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host 135-180-173-181.dsl.dynamic.sonic.net [135.180.173.181] (may be forged) claimed to be alto In-Reply-To: Your message of "Sat, 06 May 2023 10:19:35 +0300." <83ild6gc54.fsf@gnu.org> X-Mailer: MH-E 8.6+git; nmh 1.7.1; Emacs 29.0.90 Content-ID: <24737.1683411028.1@alto> Received-SPF: pass client-ip=198.144.192.42; envelope-from=kupfer@rawbw.com; helo=shell1.rawbw.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:305939 Archived-At: Eli Zaretskii wrote: > As for the "clock-out" issue: like I said, time trackers used for > tracking work activities do have both 'o' and 'O'. The former means > "end of workday", Well, timeclock also uses 'o' with timeclock-change, as in i 2023/04/25 10:49:35 task1 o 2023/04/25 11:10:15 i 2023/04/25 11:10:17 task2 o 2023/04/25 11:45:41 i 2023/04/25 11:45:44 task3 o 2023/04/25 12:10:33 i 2023/04/25 12:10:35 task2 o 2023/04/25 12:35:14 (This is an excerpt from my timelog file, with the task names genericized.) I think the multi-second gaps between "o" and "i" are from timeclock writing the "o" line and then prompting for the new task name. It seems like timelock could get the new task name first, and then write out the "o" and "i" lines with the same timestamp. mike