From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: johnw@gnu.org, q01@disroot.org, emacs-devel@gnu.org
Subject: Re: Extending timeclock.el
Date: Sat, 06 May 2023 19:22:09 +0000 [thread overview]
Message-ID: <87sfc9xo2m.fsf@localhost> (raw)
In-Reply-To: <838re1ffa0.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
It is not, AFAIU. As John Wiegley pointed, it is already used by GNU
ledger.
And wouldn't it be nice to allow timeclock to read from Org logbooks or
some third-party timelog file formats?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-05-06 19:22 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
2023-05-06 19:22 ` Ihor Radchenko [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfc9xo2m.fsf@localhost \
--to=yantar92@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=q01@disroot.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.