emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Olaf Dietsche <olaf+list.orgmode@olafdietsche.de>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Date-centric Clocktable
Date: Wed, 07 Sep 2011 15:54:34 +0200	[thread overview]
Message-ID: <87obywcvad.fsf@rat.lan> (raw)
In-Reply-To: <F3DD95C3-9812-40A7-A733-60649674BDF9@gmail.com> (Carsten Dominik's message of "Wed, 7 Sep 2011 12:28:22 +0200")

Carsten Dominik <carsten.dominik@gmail.com> writes:

> On Sep 7, 2011, at 12:16 PM, Olaf Dietsche wrote:
>
>> Rasmus <rasmus@gmx.us> writes:
>> 
>>>> Why don't you just use a simple (perl/python/...) script to collect your
>>>> data? Here's a quick hack in perl:
>>> 
>>> That was my plan if I was not able to do from within Org. To me it would
>>> be a lot faster than hacking something together in emacs-lisp,
>>> unfortunately. 
>> 
>> If you insist on elisp, maybe something along these (untested) lines
>> might work:
>> 
>> ---8<--- cut here ---
[snip]
>> --- cut here --->8---
>
> this is great!

Thank you :-)

> Maybe we should make this a little builtin function,
> with a format specification to create the lines.
> What is still missing, I think, is some sorting by time would.
> Basically, use
>
>   (org-float-time
>    (apply 'encode-time (save-match-data (org-parse-time-string (match-string 1)))))
>
> after the successful search for a clock string to get a floating
> point number representing the starting time, collect the 
> line you are creating into an alist with the times and sort
> them before inserting into the buffer.

I don't know, wether adding small special purpose functions adds real
value, since we already have "org-map-entries". Maybe adding generic
functions to org or showing lisp snippets at worg would be more useful.

Regards, Olaf

  reply	other threads:[~2011-09-07 13:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 12:33 Date-centric Clocktable Rasmus
2011-09-06 10:36 ` Bernt Hansen
2011-09-06 21:36   ` Rasmus
2011-09-06 21:47     ` Carsten Dominik
2011-09-07  8:07       ` Rasmus
2011-09-07  8:16         ` Carsten Dominik
2011-09-07 12:54           ` Giovanni Ridolfi
2011-09-07  2:08     ` Bernt Hansen
2011-09-07  8:11       ` Rasmus
2011-09-07  9:01 ` Olaf Dietsche
2011-09-07  9:09   ` Rasmus
2011-09-07 10:16     ` Olaf Dietsche
2011-09-07 10:28       ` Carsten Dominik
2011-09-07 13:54         ` Olaf Dietsche [this message]
2011-09-07 22:53           ` Rasmus
2011-09-08 13:40             ` A. Ryan Reynolds
2011-09-07 10:56       ` Rasmus
2011-09-07 11:30         ` Olaf Dietsche
2011-09-07 13:38       ` Olaf Dietsche
2011-09-07 23:38         ` Rasmus
2011-10-21 17:52 ` 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=87obywcvad.fsf@rat.lan \
    --to=olaf+list.orgmode@olafdietsche.de \
    --cc=carsten.dominik@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).