From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: johnw@gnu.org, q01@disroot.org, emacs-devel@gnu.org
Subject: Re: Extending timeclock.el
Date: Sat, 06 May 2023 22:09:27 +0300 [thread overview]
Message-ID: <838re1ffa0.fsf@gnu.org> (raw)
In-Reply-To: <871qjtz479.fsf@localhost> (message from Ihor Radchenko on Sat, 06 May 2023 18:48:26 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, John Task <q01@disroot.org>,
> emacs-devel@gnu.org
> Date: Sat, 06 May 2023 18:48:26 +0000
>
> John Wiegley <johnw@gnu.org> 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.
next prev parent reply other threads:[~2023-05-06 19:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 19:15 Extending timeclock.el John Task
2023-05-06 6:09 ` Philip Kaludercic
2023-05-06 7:19 ` Eli Zaretskii
2023-05-06 18:35 ` John Wiegley
2023-05-06 18:48 ` Ihor Radchenko
2023-05-06 18:48 ` John Wiegley
2023-05-06 19:02 ` Ihor Radchenko
2023-05-06 19:00 ` John Wiegley
2023-05-06 19:09 ` Eli Zaretskii [this message]
2023-05-06 19:22 ` Ihor Radchenko
2023-05-06 19:23 ` John Wiegley
2023-05-06 22:10 ` Mike Kupfer
2023-05-09 16:44 ` Mike Kupfer
-- strict thread matches above, loose matches on Subject: below --
2023-05-06 15:47 John Task
2023-05-06 16:53 ` Eli Zaretskii
2023-05-06 16:46 John Task
2023-05-06 18:35 John Task
2023-05-06 19:21 John Task
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838re1ffa0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=q01@disroot.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).