From mboxrd@z Thu Jan 1 00:00:00 1970 From: meingbg Subject: clock *list* Date: Thu, 20 Aug 2009 18:25:38 +0200 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0133905753==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MeASN-0005Zq-W1 for emacs-orgmode@gnu.org; Thu, 20 Aug 2009 12:25:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MeASM-0005Wd-LB for emacs-orgmode@gnu.org; Thu, 20 Aug 2009 12:25:43 -0400 Received: from [199.232.76.173] (port=41514 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MeASM-0005W0-4N for emacs-orgmode@gnu.org; Thu, 20 Aug 2009 12:25:42 -0400 Received: from ey-out-1920.google.com ([74.125.78.150]:35739) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MeASL-0002ge-8s for emacs-orgmode@gnu.org; Thu, 20 Aug 2009 12:25:41 -0400 Received: by ey-out-1920.google.com with SMTP id 5so43421eyb.24 for ; Thu, 20 Aug 2009 09:25:38 -0700 (PDT) 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 --===============0133905753== Content-Type: multipart/alternative; boundary=000e0cd1d55abb3d46047195336c --000e0cd1d55abb3d46047195336c Content-Type: text/plain; charset=ISO-8859-1 Sometimes I find myself in the need of a clocklist (or clock log if you prefer) rather than a clock table, that is a list of the clock lines (cutting out any text after the "^\ *CLOCK\:\ ") with the path added to the end, ordered by the clock start time in decending order. It would be great to have this feature as a dynamic block function, (defun org-dblock-write:clocklist....). The scope and block parameters from clocktable would also be of great benefit. If the scope parameter is implemented the path should probably be relative to that scope. Below is an example of how I'd imagine the result. Is this a good idea at all? Would it be hard to implement? //meingbg ---BEGIN EXAMPLE ORG FILE--- * a any clock lines under this heading are not included * b CLOCK: [2009-08-20 Thu 12:53]--[2009-08-20 Thu 12:54] no colon #+BEGIN: clocklist :scope tree :block 2009-08 [2009-08-20 Thu 12:58]--[2009-08-20 Thu 12:59] comment : d/f [2009-08-20 Thu 12:56]--[2009-08-20 Thu 12:57] => 0:01 : d/f [2009-08-20 Thu 12:54]--[2009-08-20 Thu 12:55] => 0:01 : d [2009-08-20 Thu 12:53]--[2009-08-20 Thu 12:54] no colon [2009-08-20 Thu 12:52]--[2009-08-20 Thu 12:53] => 0:01 : c [2009-08-20 Thu 12:50]--[2009-08-20 Thu 12:51] => 0:01 : c #+END ** c :CLOCK: CLOCK: [2009-08-20 Thu 12:52]--[2009-08-20 Thu 12:53] => 0:01 CLOCK: [2009-08-20 Thu 12:50]--[2009-08-20 Thu 12:51] => 0:01 :END: text ** d CLOCK: [2009-08-20 Thu 12:54]--[2009-08-20 Thu 12:55] => 0:01 *** f :CLOCK: CLOCK: [2009-08-20 Thu 12:58]--[2009-08-20 Thu 12:59] comment CLOCK: [2009-08-20 Thu 12:56]--[2009-08-20 Thu 12:57] => 0:01 :END: ---END EXAMPLE ORG FILE--- --000e0cd1d55abb3d46047195336c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Sometimes I find myself in the need of a clocklist (or clock log if yo= u prefer) rather than a clock table, that is a list of the clock lines (cut= ting out any text after the "^\ *CLOCK\:\ ") with the path added = to the end, ordered by the clock start time in decending order. It would be= great to have this feature as a dynamic block function, (defun org-dblock-= write:clocklist....). The scope and block parameters from clocktable would = also be of great benefit. If the scope parameter is implemented the path sh= ould probably be relative to that scope.

Below is an example of how I'd imagine the result. = Is this a good idea at all? Would it be hard to implement?

//meingbg


---BEGIN EXAMPLE ORG FILE---
* a
any clock lines under this heading are not included
* b
= =A0=A0CLOCK: = [2009-08-20 Thu 12:53]--[2009-08-20 Thu 12:54] no colon
=
#+BEGIN: clocklist :scope tree :block 2009-08
[2009-08-20 Thu 12:58]--[2009-08-20 Thu 12:59] comment : = d/f
[2009-08-= 20 Thu 12:56]--[2009-08-20 Thu 12:57] =3D> =A00:01 : d/f
= [2009-08-20 Th= u 12:54]--[2009-08-20 Thu 12:55] =3D> =A00:01 : d
[2009-08-20 = Thu 12:53]--[2009-08-20 Thu 12:54] no colon
[2009-08-= 20 Thu 12:52]--[2009-08-20 Thu 12:53] =3D> =A00:01 : c
[2009-0= 8-20 Thu 12:50]--[2009-08-20 Thu 12:51] =3D> =A00:01 : c
#+END
** c
=A0=A0 :C= LOCK:
=A0=A0 CLOCK: [2009-08-20 Thu 12:52]--[2009-08-20 Thu 12:53= ] =3D> =A00:01
=A0=A0 CL= OCK: [2009-08-20 Thu 12:50]--[2009-08-20 Thu 12:51] =3D> =A00:01<= /font>
=A0=A0 :E= ND:
text
** d
=A0=A0 CLOCK: [2009-08-20 Thu 12:54]--[2009-08-20 Thu 12:55] =3D> = =A00:01
*** f
=A0=A0 =A0:CLOCK:
=A0=A0 = =A0CLOCK: [2009-08-20 Thu 12:58]--[2009-08-20 Thu 12:59] comment
= =A0=A0 =A0CLOC= K: [2009-08-20 Thu 12:56]--[2009-08-20 Thu 12:57] =3D> =A00:01
= =A0=A0 =A0:END= :
---END EXAMPLE ORG FILE---
--000e0cd1d55abb3d46047195336c-- --===============0133905753== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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 --===============0133905753==--