From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: monthly report Date: Thu, 19 Mar 2009 11:13:14 +0100 Message-ID: <7E648EF2-EEE9-4A12-A32A-D57C5D0958A5@uva.nl> References: <86ps4pbrxy.fsf@bitty.lumos.us> <7b72afe87a251d7615438346906a6f1f@science.uva.nl> <87hc1sdjo8.fsf@pond.riseup.net> <37A74413-AC81-4F69-A08D-FD1D0DB08AE0@uva.nl> <20090318145725.GD18443@pond.riseup.net> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LkLDM-0004nu-3V for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:35:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LkLDH-0004iH-1E for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:35:27 -0400 Received: from [199.232.76.173] (port=42180 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LkLDG-0004hy-Q1 for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:35:22 -0400 Received: from mail-bw0-f167.google.com ([209.85.218.167]:37510) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LkLDG-0002y4-8g for emacs-orgmode@gnu.org; Thu, 19 Mar 2009 12:35:22 -0400 Received: by bwz11 with SMTP id 11so528178bwz.42 for ; Thu, 19 Mar 2009 09:35:21 -0700 (PDT) In-Reply-To: <20090318145725.GD18443@pond.riseup.net> 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: Micah Anderson Cc: emacs-orgmode@gnu.org On Mar 18, 2009, at 3:57 PM, Micah Anderson wrote: > * Carsten Dominik [2009-03-18 04:42-0400]: >> >> On Mar 17, 2009, at 8:38 PM, Micah Anderson wrote: >>> Carsten Dominik 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? > > [snip: lisp function (26 lines)] > >>> 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. >> >> It seems that you are specifying the date in an invalid way. >> What are you typing when prompted for a date? > > Ok, I restarted emacs and tried again, and now I am not given this > mini-buffer message at all. On restart, I found an error in my .emacs, > which could have been causing this issue. Chalk that up to confused > internal state I guess. > > However, org-closed-in-range still doesn't seem to be doing anything > interesting, as far as I can tell. It folded up my org file, but thats > about it. Do you have CLOSED: <....> timestamps in the buffer? You do get these by setting (setq org-log-done 'time) or by doing #+STARTUP: logdone - Carsten > > Maybe there is a better way for me to get at what I want, and I just > haven't found it yet (I am pretty new at org) and debugging this might > not be the best thing to do if there is something better to solve my > need. I basically just need to, at the end of the week, produce a > report > of what I've worked on for that week, both things I finished, but also > things that are still in progress. Including the time spent is useful > too. I can go into the agenda and hit 'R' to get a time-table at the > end > of the page, but I need a more granual day-by-day breakdown (Monday: > 4hrs, worked on X, Y and completed Z). You can configure the clock report to be delivered for days by setting the :step day property in org-agenda-clock-report-parameter-plist Or you can switch to a daily agenda (the "d") key and look at the clock report day by day. Pressing "l" or "C-u l" turns on the log info for days, showing you what you did on a particular day, provided that you have recorded that informtation by setting org-log-done, of by clocking time, or by recording state changes. All this is in the manual. HTH - Carsten > > thanks for your response! > micah