From: Bernt Hansen <bernt@norang.ca>
To: David Frascone <dave@frascone.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Final Question: Usage
Date: Wed, 28 Apr 2010 17:31:30 -0400 [thread overview]
Message-ID: <874oivs1ql.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <v2q9cf5ced21004281057n3612c4d7rd2b5dfd911b0a775@mail.gmail.com> (David Frascone's message of "Wed\, 28 Apr 2010 11\:57\:51 -0600")
David Frascone <dave@frascone.com> writes:
> I'm still using a monolithic file to inplement my DGTD (Dave's GTD).
> I'm not as anal as TOD (The other Dave, Dave Allen), and I don't run a
> strict inbox.
>
> What I do want is:
> 1) a place to keep track of live projects, bugs, conversations, etc.
> 2) A place for notes
> 3) A place to track TODO's
> 4) A way to archive off done stuff.
>
> So far, orgmode does the above with ease. But, I am starting to run
> into walls.
>
> Organization: I'm using one monolithic file now. And, agenda mode
> doesn't know about it till I add it. Should I be using agenda mode to
> track todos? (This goes with my calendar questions a bit in the other
> mail). If I do use agenda mode, how do I add multiple files?
>
> How do I work with multiple files? Is there an easy way to jump back
> and forth from them, if I start making one file for Bugs, one for
> Escalations, one for projects, one for notes, etc?
>
> Finally -- and this is my biggest stumbling block: Status reporting
> I'm looking for some way to generate a status report of what I've been
> working on. So, this report should contain anything that has been
> modified in the last week. (I drop date stamps a lot). Also, the
> report should include extra flagged items, even if they did not get
> work. (i.e. Background tasks that are starving should be noted --
> but, since not all tasks / entries are background tasks, I'd make some
> custom tag, like, "reportme" that should be reported, regardless)
>
> I'm trying to generate a status view like that, export to HTML, and
> e-mail it to my pointy haired boss . . . . any way to do that?
>
The agenda is your friend. You can have multiple files in the agenda
all contributing to views of your todo lists in agenda views.
C-c [ adds the current file to org-agenda-files so just visit multiple
files you want in your agenda and C-c [ once in each.
Now C-c a t will show all todos in all your files. C-c a a shows a
calendar view (day/week).
I navigate to things only from the agenda.
You'll want log view in the agenda or something similar for status
reporting. You can export agenda views but I've never done it :)
HTH,
Bernt
next prev parent reply other threads:[~2010-04-28 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 17:57 Final Question: Usage David Frascone
2010-04-28 20:01 ` Nathan Neff
2010-04-28 21:31 ` Bernt Hansen [this message]
2010-04-29 8:43 ` Sven Bretfeld
2010-04-29 21:23 ` Stephan Schmitt
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=874oivs1ql.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=dave@frascone.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).