From: Russell Adams <RLAdams@adamsinfoserv.com>
To: emacs-orgmode@gnu.org
Subject: Re: Alternatives to clocking in/out for reporting time
Date: Thu, 30 Jun 2022 10:57:04 +0200 [thread overview]
Message-ID: <Yr1lYINKoYSy6139@tahm> (raw)
In-Reply-To: <CAJcAo8tkhdY6Z-UkFhb81Y06gihbGrTkKzCPbrtQG1EzJnj1Gg@mail.gmail.com>
On Wed, Jun 29, 2022 at 07:11:10PM -0700, Samuel Wales wrote:
> a few things taht are probably all completely obvious or investigated
> or irrelevant just in case. just brainstorm.
I appreciate that! That's really what I'm asking for is ideas. I don't
mind writing a bit of code, but I'm not sure where to start.
> do you have everything relevant in the same subtrees? i.e. not
> wanting granular, can you search upward for a dominating entry kind of
> like git searching upward for the .git dir or so? property drawer
> could control what's a dominating entry. you probably thoguht of this
> or of having whatever categories as tags or categories in entries
> though. in any case that would clock. you could even have clocking
> clock into that no matter wher eyou are via some timer in principle.
> just a brainstorm. you said dynamic som perhaps there is no
> dominating entry for each category though.
The core issue is I want to report on total time as an aggregate, not
on time per task. Clock reporting gives me precise time accounting for
a specific task. I want to fill whole hours with whatever tasks
happened at those times chronologically.
> org-time-stamp-rounding-minutes and org-clock-rounding-minutes . i
> presume you don't find them relevant.
I saw that. Interesting they don't appear to change the result, they
modify the input when you record the time by rounding.
> reminder: inactive ts in the clocked notation is usualy treated
> separately by org [i.e. not hte same type of ts] from bare ia.
I had considered perhaps converting inactive timestamps into clocking
records. Unfortunately I think the core issue remains in aggregating
by task, not by time.
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
https://www.adamsinfoserv.com/
next prev parent reply other threads:[~2022-06-30 9:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 14:59 Alternatives to clocking in/out for reporting time Russell Adams
2022-06-29 21:26 ` Tim Cross
2022-06-29 22:09 ` Russell Adams
2022-06-30 2:11 ` Samuel Wales
2022-06-30 2:12 ` Samuel Wales
2022-06-30 8:57 ` Russell Adams [this message]
2022-06-30 22:32 ` Samuel Wales
2022-07-08 7:02 ` Ihor Radchenko
2022-07-08 8:10 ` Russell Adams
2022-07-09 4:00 ` Ihor Radchenko
2022-07-09 12:44 ` Russell Adams
2022-07-10 9:30 ` Ihor Radchenko
2022-07-10 23:09 ` Samuel Wales
2022-07-10 12:26 ` Olaf Dietsche
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yr1lYINKoYSy6139@tahm \
--to=rladams@adamsinfoserv.com \
--cc=emacs-orgmode@gnu.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/org-mode.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).