From: Kyle Farrell <kaf@nwlink.com>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: export weekly completed/late items
Date: Tue, 8 Feb 2011 11:30:57 -0800 [thread overview]
Message-ID: <19793.39409.384877.468341@bitter.patentinvestor.com> (raw)
In-Reply-To: <AANLkTimsFnuzd7d=YOKhiQyiu32+bgdzC2_KP92brnO_@mail.gmail.com>
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 <kaf@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
> >
>
next prev parent reply other threads:[~2011-02-08 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 20:04 export weekly completed/late items Kyle Farrell
2011-02-08 18:14 ` Marcelo de Moraes Serpa
2011-02-08 19:30 ` Kyle Farrell [this message]
2011-02-09 15:36 ` Christopher Allan Webber
2011-02-09 16:41 ` Marcelo de Moraes Serpa
2011-02-09 16: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=19793.39409.384877.468341@bitter.patentinvestor.com \
--to=kaf@nwlink.com \
--cc=celoserpa@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).