emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: meingbg <meingbg@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: clock *list*
Date: Thu, 20 Aug 2009 18:25:38 +0200	[thread overview]
Message-ID: <e83e84da0908200925o488f1553wa86e5c5838c059e4@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1661 bytes --]

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---

[-- Attachment #1.2: Type: text/html, Size: 6078 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
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

             reply	other threads:[~2009-08-20 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20 16:25 meingbg [this message]
2009-08-23  5:29 ` clock *list* Bastien

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=e83e84da0908200925o488f1553wa86e5c5838c059e4@mail.gmail.com \
    --to=meingbg@gmail.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).