From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell Adams Subject: Re: Re: Publishing clocked time Date: Fri, 11 Sep 2009 00:05:34 -0500 Message-ID: <20090911050534.GZ18897@thinkpad.adamsinfoserv.com> References: <566e527b0909040832v2dd07dadm89168f8aaedea3d2@mail.gmail.com> <877hwabwdf.fsf@mundaneum.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MlyKN-0007An-Dh for emacs-orgmode@gnu.org; Fri, 11 Sep 2009 01:05:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MlyKM-0007AV-Mh for emacs-orgmode@gnu.org; Fri, 11 Sep 2009 01:05:42 -0400 Received: from [199.232.76.173] (port=57618 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlyKM-0007AM-DV for emacs-orgmode@gnu.org; Fri, 11 Sep 2009 01:05:42 -0400 Received: from squirtle.drak.net ([72.52.144.201]:56600) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MlyKL-0000RJ-SX for emacs-orgmode@gnu.org; Fri, 11 Sep 2009 01:05:42 -0400 Received: from 206.180.154.148.adsl.hal-pc.org ([206.180.154.148] helo=localhost) by squirtle.drak.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1MlyKH-0002fX-Sf for emacs-orgmode@gnu.org; Fri, 11 Sep 2009 00:05:38 -0500 Content-Disposition: inline In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Sorry, I think I'd chipped in here at one point, the idea is for routine "timecards" a simple list of hours aggregated by date would be useful. I could see aggregate hours for task by ALL dates unless otherwise specified. * Timecard ** Customer X CLOCK: [2009-09-01 Thu 09:00]--[2009-09-01 Thu 12:00] => 3:00 CLOCK: [2009-09-02 Thu 09:00]--[2009-09-02 Thu 12:00] => 3:00 CLOCK: [2009-09-03 Thu 09:00]--[2009-09-03 Thu 12:00] => 3:00 CLOCK: [2009-09-04 Thu 09:00]--[2009-09-04 Thu 12:00] => 3:00 CLOCK: [2009-09-05 Thu 09:00]--[2009-09-05 Thu 12:00] => 3:00 CLOCK: [2009-09-01 Thu 12:00]--[2009-09-01 Thu 17:00] => 5:00 CLOCK: [2009-09-02 Thu 12:00]--[2009-09-02 Thu 17:00] => 5:00 CLOCK: [2009-09-03 Thu 12:00]--[2009-09-03 Thu 17:00] => 5:00 CLOCK: [2009-09-04 Thu 12:00]--[2009-09-04 Thu 17:00] => 5:00 CLOCK: [2009-09-05 Thu 12:00]--[2009-09-05 Thu 17:00] => 5:00 #+BEGIN timecard |------------+------------+---------| | *Date* | *Task* | *Hours* | |------------+------------+---------| | 2009-09-01 | Customer X | 8 | | 2009-09-02 | Customer X | 8 | | 2009-09-03 | Customer X | 8 | | 2009-09-04 | Customer X | 8 | | 2009-09-05 | Customer X | 8 | |------------+------------+---------| | *Total* | | 40 | |------------+------------+---------| #+END I would anticipate that it may be optional to sort by date or by task (if you include sublevels), though I have mixed feelings about adding subtotal lines between aggregates. Comments? FYI, I'm learning LISP as we speak! Perhaps I can start customizing things soon! On Fri, Sep 11, 2009 at 05:51:45AM +0200, Carsten Dominik wrote: > > On Sep 7, 2009, at 5:35 PM, S?bastien Vauban wrote: > >> Hi Carsten, >> >> Carsten Dominik wrote: >>> On Sep 4, 2009, at 5:32 PM, Ivan Chernetsky wrote: >>>> >>>> is it possible to publish clocked time of a TODO item? >>> >>> clocking lines are considered ugly and are therefore not included >>> during >>> publishing. I could make an option for it... Are there more people >>> interested? >> >> Yes, quite interested, even if not absolutely required. >> >> I needed that when I transferred my "billing" info to our company's >> accountant, so that she was able to correctly bill the clients, and >> check that >> I worked enough time on the month. >> >> However, as the LaTeX export was quite empty of those info, I switched >> back to >> sending the info as plain text email. >> >> Though, would that be available, yes, I would definitely use it... > > No a single post in this thread does explain what exactly would be > useful.. :-( > > - Carsten > > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > ------------------------------------------------------------------ Russell Adams RLAdams@AdamsInfoServ.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3