emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Micah Anderson <micah@riseup.net>
To: emacs-orgmode@gnu.org
Subject: Re: monthly report
Date: Tue, 17 Mar 2009 15:38:15 -0400	[thread overview]
Message-ID: <87hc1sdjo8.fsf@pond.riseup.net> (raw)
In-Reply-To: 7b72afe87a251d7615438346906a6f1f@science.uva.nl

Hi all, apologies for resurrecting an older thread, but I was searching
for this very capability and found this post.

Carsten Dominik <dominik@science.uva.nl> writes:
> On May 25, 2007, at 3:41, Steven Lumos wrote:
>> Being yet another planner switcher, I'm used to using planner-report-
>> generate to assist me with writing a monthly activity report.  I don't
>> need fine-grained time tracking, or even most of what planner-report-
>> generate does--it would be ideal to get just a list of TODOs that were
>> closed between two dates and then I'll look at it while I type a few
>> sentences in an email buffer.
>> Is there already an easy way to "get a list" (I guess that a sparse
>> tree would be most convenient for me) of TODOs marked as closed within
>> some date range?

I have been trying to figure this one out myself. Thank goodness for
list archives!

> You can use org-occur to create a tree with matches of CLOSED time
> stamps.
> And you can use the callback argument of org-occur to verify if a
> match is in a given time interval.  Something like this:
> (defun org-closed-in-range ()
>   "Sparse treee of items closed in a certain time range."
>   (interactive)
>   ;; Get the time interval from the user.
>   (let* ((time1 (time-to-seconds
>                  (org-read-date nil 'to-time nil "Starting date: ")))
>          (time2 (time-to-seconds
>                  (org-read-date nil 'to-time nil "End date:")))
>          ;; callbakc function
>          (callback (lambda ()
>                      (let ((time
>                             (time-to-seconds
>                              (apply 'encode-time
>                                     (org-parse-time-string
>                                      (match-string 1))))))
>                        ;; check if time in interval
>                        (and (>= time time1) (<= time time2))))))
>     ;; make tree, check each match with the callback
>     (org-occur "CLOSED: +\\[\\(.*?\\)\\]" nil callback)))

Ok, I tried this and I'm not sure what it did, if anything. I get the
mini-buffer saying, 'Specified time is not representable' I've tried
various date range possibilities, and can't get it to work.

I did also change the '(org-occur "CLOSED: +\\[\\(.*?\\)\\]" nil
callback)))' to be instead '(org-occur "DONE +\\[\\(.*?\\)\\]" nil
callback)))' due to the way my org seems to represent finished items:

** DONE fix the apt puppet module to automatically add apt-keys, publish that new repository and deploy
   SCHEDULED: <2009-03-16 Mon>
   - State "DONE"       [2009-03-16 Mon 14:49] \\
     made this a lot nicer
   CLOCK: [2009-03-16 Mon 14:21]--[2009-03-16 Mon 14:21] =>  0:00
   [2009-03-16 Mon]

As far as I can tell, I did not setup this format. I tried to change the
(org-occur "CLOSED... to be "DONE..." instead, but no change here

Thanks for any help!

  parent reply	other threads:[~2009-03-17 20:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25  1:41 monthly report Steven Lumos
2007-05-25 13:29 ` Jason F. McBrayer
2007-05-29 12:29 ` Carsten Dominik
2007-05-30  0:30   ` Steven Lumos
2009-03-17 19:38   ` Micah Anderson [this message]
2009-03-18  8:42     ` Carsten Dominik
2009-03-18 14:57       ` Micah Anderson
2009-03-19 10:13         ` Carsten Dominik
  -- strict thread matches above, loose matches on Subject: below --
2015-08-10 17:27 Monthly report Norbert

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:

  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=87hc1sdjo8.fsf@pond.riseup.net \
    --to=micah@riseup.net \
    --cc=emacs-orgmode@gnu.org \


* 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


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