Christopher, thank you very much! Although I have been using org for quite some time, I never really spend time going through the manual and learning all the nuances of the agenda, and I often forget how powerful it is.
It would really nice if we had an agenda command to export all of this as a PDF report, for example. Cheers, Marcelo. On Wed, Feb 9, 2011 at 9:36 AM, Christopher Allan Webber <cweb...@dustycloud.org> wrote: > I do this for generating work reports, but all I do is > > #+begin_src emacs-lisp > (setq org-log-done 'time) > (setq org-log-state-notes-into-drawer t) > #+end_src > > To enable logging (second line is to prevent cluttering things up) > > Then in the agenda: > > press "v l" to enable logging > press "v a" to enable archived trees > press "b" to go back a week. > > It also helps that I have > > #+begin_src emacs-lisp > ; Start weekly view from present day > (setq org-agenda-start-on-weekday nil) > #+end_src > > set so that the agenda starts on the current day. > > I usually end up generating reports for the last two weeks... I've > considered looking to see if there's a way to set up agenda commands to > generate a list of the last two weeks' tasks so I didn't have to press > back twice, but I haven't tried yet :) > > Does that help? > - cwebb > > Kyle Farrell <k...@nwlink.com> writes: > >> I'm a bit of a newbie to org-mode, so where should I start to look at >> this? Is there existing functionality in either org-agenda or >> org-export that would be a good starting point? >> >> >> Marcelo de Moraes Serpa wrote: >>> This is a great idea, and one I would use myself. I don't think you >>> could configure the agenda to build something like that though, I'd >>> say we'd need to come up with some custom elisp code or a script that >>> parses the org archive file and does the dirty job. >>> >>> Marcelo. >>> >>> On Mon, Feb 7, 2011 at 2:04 PM, Kyle Farrell <k...@nwlink.com> wrote: >>> > I'm trying to create a weekly report of items completed or >>> > outstanding. I'd like to bucket these by status. I've got my entries >>> > with a DEADLINE calendar date set. >>> > >>> > For example given the org input: >>> > >>> > * TODO Fix bug for software project X >>> > DEADLINE: <2011-02-07 Mon> >>> > * DONE Update documentation for feature Y >>> > DEADLINE: <2011-02-09 Wed> >>> > * DONE Scope out new version of Z >>> > DEADLINE: <2011-02-09 Wed> >>> > * TODO Code new version of Z >>> > DEADLINE: <2011-02-17 Thu> >>> > >>> > I'd like to bucketize these based on the current date TODO status. If >>> > the date is 2/11/2011, based on the deadline and the status I'd like >>> > to see: >>> > >>> > Missed: >>> > 2011-02-07: Fix bug for software project X >>> > >>> > Completed: >>> > 2011-02-09: Update documentation for feature Y >>> > 2011-02-09: Scope out new version of Z >>> > >>> > Coming up: >>> > 2011-02-17: Code new version of Z >>> > >>> > >>> > Am I best using an agenda view to create this? Or would this be in a >>> > custom exporter? >>> > >>> > thanks! >>> > -Kyle >>> > >>> > _______________________________________________ >>> > Emacs-orgmode mailing list >>> > Please use `Reply All' to send replies to the list. >>> > Emacs-orgmode@gnu.org >>> > http://lists.gnu.org/mailman/listinfo/emacs-orgmode >>> > >>> >> >> _______________________________________________ >> Emacs-orgmode mailing list >> Please use `Reply All' to send replies to the list. >> Emacs-orgmode@gnu.org >> http://lists.gnu.org/mailman/listinfo/emacs-orgmode >> > > -- > 𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻 > _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode