all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mike Kupfer <kupfer@rawbw.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: John Task <q01@disroot.org>,
	emacs-devel@gnu.org, John Wiegley <johnw@gnu.org>
Subject: Re: Extending timeclock.el
Date: Sat, 06 May 2023 15:10:28 -0700	[thread overview]
Message-ID: <24738.1683411028@alto> (raw)
In-Reply-To: Your message of "Sat, 06 May 2023 10:19:35 +0300." <83ild6gc54.fsf@gnu.org>

Eli Zaretskii wrote:

> As for the "clock-out" issue: like I said, time trackers used for
> tracking work activities do have both 'o' and 'O'.  The former means
> "end of workday", 

Well, timeclock also uses 'o' with timeclock-change, as in

i 2023/04/25 10:49:35 task1
o 2023/04/25 11:10:15
i 2023/04/25 11:10:17 task2
o 2023/04/25 11:45:41
i 2023/04/25 11:45:44 task3
o 2023/04/25 12:10:33
i 2023/04/25 12:10:35 task2
o 2023/04/25 12:35:14

(This is an excerpt from my timelog file, with the task names
genericized.)

I think the multi-second gaps between "o" and "i" are from timeclock
writing the "o" line and then prompting for the new task name.  It seems
like timelock could get the new task name first, and then write out the
"o" and "i" lines with the same timestamp.

mike



  parent reply	other threads:[~2023-05-06 22:10 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 [this message]
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=24738.1683411028@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 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.