From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Extending timeclock.el Date: Sat, 06 May 2023 22:09:27 +0300 Message-ID: <838re1ffa0.fsf@gnu.org> References: <861qjubmzp.fsf@disroot.org> <83ild6gc54.fsf@gnu.org> <871qjtz479.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19299"; mail-complaints-to="usenet@ciao.gmane.io" Cc: johnw@gnu.org, q01@disroot.org, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 06 21:09:03 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 1pvNHC-0004lT-1G for ged-emacs-devel@m.gmane-mx.org; Sat, 06 May 2023 21:09:02 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pvNGj-0004nx-Ax; Sat, 06 May 2023 15:08:33 -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 1pvNGg-0004ly-Sf for emacs-devel@gnu.org; Sat, 06 May 2023 15:08:30 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pvNGg-0007Wu-JM; Sat, 06 May 2023 15:08:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=xQGhgl2RrZnnTJJ0Kx59hM+HQzuODmNvALM+Yu1znSY=; b=ddAJJd32cyDK mIkSm7D5f4Rs/LsMgugzyWYIyX7+qA6qnNO1O+pIwOeZa9NwA/pG2BC5UWDqoCXXFaX99RKlYHjcR T6Lap4KD3RZIHdbozzuIK3vrDw2hpChjDkFXAOEC16o3zHCIqy4HNwMn7O9lcAYUtjFtBlyhh0mb4 qzUw1xPhx2dpcYQVU77shj5DAllPoi7k06LaYpZ3CsrzfqFC+LiK4oox/WJ25nSvC/w++nvu2xjeo Zr+K6xnvGbggf83Yt6crBLTg0XQJK2qxM13Xvui7msdn1gI7NQ6vJDRiKWBhdvGbusiJRXLFQYgvz Zvf3e+vT/5gach1qUWx/LA==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pvNGg-0006Ds-08; Sat, 06 May 2023 15:08:30 -0400 In-Reply-To: <871qjtz479.fsf@localhost> (message from Ihor Radchenko on Sat, 06 May 2023 18:48:26 +0000) 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:305929 Archived-At: > From: Ihor Radchenko > Cc: Eli Zaretskii , John Task , > emacs-devel@gnu.org > Date: Sat, 06 May 2023 18:48:26 +0000 > > John Wiegley writes: > > > 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. > > Ideally, one should be able to customize how to parse and write the > format. Doesn't make a lot of sense to me: the timelog file is the internal implementation detail of timeclock.el, and doesn't need to support user customization of the format.