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 00:09:09 +0200 [thread overview]
Message-ID: <YrzNhWS/H5udfcLY@tahm> (raw)
In-Reply-To: <87v8sji1v3.fsf@gmail.com>
On Thu, Jun 30, 2022 at 07:26:20AM +1000, Tim Cross wrote:
> > The point is that I'm not worried about accounting time by task,
> > instead I'm aggregating tasks into accounting by whole hours.
> >
> > I'm looking at org-element, and it appears I'd have to do my own
> > agenda style scan of the whole tree to find items to classify by
> > hour. While I'm somewhat proficient at elisp, that sounds like a steep
> > wall to climb.
> >
> > Is there an iterative way to review items in an agenda view so I can
> > do the math to produce a report?
> >
>
> Russell,
>
> I don't have an answer for your specific problem. However, I was
> wondering if you looked at the options to configure the built-in time
> clocking and report table?
I've looked at it several times, and it just doesn't fit the bill.
Sorry.
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
https://www.adamsinfoserv.com/
next prev parent reply other threads:[~2022-06-29 22:10 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 [this message]
2022-06-30 2:11 ` Samuel Wales
2022-06-30 2:12 ` Samuel Wales
2022-06-30 8:57 ` Russell Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YrzNhWS/H5udfcLY@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 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.