From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: John Task Newsgroups: gmane.emacs.devel Subject: Re: Extending timeclock.el Date: Sat, 06 May 2023 16:21:22 -0300 Message-ID: <86fs899s9p.fsf@disroot.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8470"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: John Wiegley Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 06 21:40:44 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 1pvNlr-00022Y-MJ for ged-emacs-devel@m.gmane-mx.org; Sat, 06 May 2023 21:40:43 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pvNlN-0004xo-31; Sat, 06 May 2023 15:40:13 -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 1pvNWY-000219-Qo for emacs-devel@gnu.org; Sat, 06 May 2023 15:24:55 -0400 Original-Received: from knopi.disroot.org ([178.21.23.139]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pvNWX-000260-4k; Sat, 06 May 2023 15:24:54 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id EB80540205; Sat, 6 May 2023 21:24:44 +0200 (CEST) X-Virus-Scanned: SPAM Filter at disroot.org Original-Received: from knopi.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EYCPkw5NleAW; Sat, 6 May 2023 21:24:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1683401083; bh=S4uI0lTiOFmQ+9Snuj24zov823UlH1mG4m/RcIecU9k=; h=From:To:Cc:Subject:In-Reply-To:Date; b=ZkWFx7zsKyyaD5qW83A0M9dIO0IpqHDPybbnzp7VI9ExhfOw0+nczUCLj9dabS5Rs NlDzubVN6PK+GGL/uLClPAaA9sJdXdfWQkuQKXNnaB1dvS4I2axu8NUpwIXfwTN1Ki wCrTq06P4PUb1WhLnjhQ2et+4og/ATg02o1XOzVzcDFG704FMxCHjgUiVFnqoriNAW wFmiy8ZQxfPERwU7Asll+3AE3Oa8dS2Ea+lYxehgt7BTO0LK+IjnYY6HlpZYcNdASR 6qRVB1v5WyE/nL0oPT4nLbVu/F5GKirPKEFmNUktOaanEYlAsdDvWXdi/aa0jf6wJX LPwPErAPe0yWA== In-Reply-To: m2jzxl1f65.fsf@newartisans.com Received-SPF: pass client-ip=178.21.23.139; envelope-from=q01@disroot.org; helo=knopi.disroot.org 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, 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-Mailman-Approved-At: Sat, 06 May 2023 15:40:11 -0400 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:305935 Archived-At: John Wiegley writes: > Hi fellow John Hello. Thanks for the quick reply. > If you do extend the _format_, it's likely you may break some of the other > tools that process timelog data. So if you choose to make an enriched format, > it would be useful if you provided a way to export this data back to flat > timelog form (such as by stripping comments). Then I could go from > timeclock-modern format -> timeclock format -> ledger, for example. I have thought about this issue, too. In principle, the format should remain unchanged _unless_ the user opts into the new workflow I'll add, which indeed is not backward compatible. If the user doesn't do so, the only new thing will be statistic reports and a parser they can use with their existent timelog files, again without any changes. Regarding the export option, I haven't thought about that, but it should be feasible. So, if you think users who opt into the new behaviour would also like to retain a way to use that data with existent tools, I'll work in that. But keep in mind that such data could be pretty different to that of other timeclock users, because they won't track, say, 8 hours per day, but rather pretty much everything they do. Best regards.