From: Mike Kupfer <kupfer@rawbw.com>
To: emacs-devel@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>, John Task <q01@disroot.org>,
John Wiegley <johnw@gnu.org>
Subject: Re: Extending timeclock.el
Date: Tue, 09 May 2023 09:44:35 -0700 [thread overview]
Message-ID: <12874.1683650675@alto> (raw)
In-Reply-To: My message of "Sat, 06 May 2023 15:10:28 -0700." <24738.1683411028@alto>
Mike Kupfer wrote:
> Well, timeclock also uses 'o' with timeclock-change
I got an off-list reply to this from Davis Herring <herring@lanl.gov>.
Davis has some technical difficulties posting to emacs-devel, so I'm
posting some excerpts here, in case anyone would like to follow up with
him.
Davis wrote:
> Since we're talking about extending timeclock: I rewrote
> timeclock-change years ago to emit a single "c" line rather than have an
> "o" with no reason and an "i" (with a different time). Part of the
> reason for this was to reduce the time spent reading the file: mine
> covers several years of work and is 30k lines with "c"s.
>
> Obviously I'd be glad to contribute this if anyone else cares for it.
He also thought that "c" might be a better fit for the track-everything
workflow.
mike
next prev parent reply other threads:[~2023-05-09 16:44 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
2023-05-06 19:23 ` John Wiegley
2023-05-06 22:10 ` Mike Kupfer
2023-05-09 16:44 ` Mike Kupfer [this message]
-- 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=12874.1683650675@alto \
--to=kupfer@rawbw.com \
--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 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).