From: Adam Spiers <orgmode@adamspiers.org>
To: emacs-orgmode@gnu.org
Subject: Re: GTD: Solving the bottleneck of converting incoming mails to NEXT actions
Date: Tue, 25 Sep 2007 00:04:59 +0100 [thread overview]
Message-ID: <20070924230459.GB9383@atlantic.linksys.moosehall> (raw)
In-Reply-To: <20070924225226.GA9383@atlantic.linksys.moosehall>
Adam Spiers (orgmode@adamspiers.org) wrote:
> On Mon, Sep 24, 2007 at 10:44:44PM +0200, Georg C. F. Greve wrote:
> > Hi all,
> >
> > I've now been using Org mode for a couple of months and am quite happy
> > with it in most ways, with conversion of incoming emails into NEXT
> > actions being the main bottleneck.
[snipped]
> > I wonder whether anyone solved this issue already.
>
> Yes, I used to have this very same bottleneck. It's not perfect yet,
> but a lot better than it used to be.
>
> I posted details in a previous thread on this list about how I use a
> combination of mutt, mairix, shell wrappers, and elisp to extract a
> mairix:$message_id style hyperlink from the currently viewed mail
> within mutt, and then yank it into my TODO.org emacs buffer, manually
> creating structure around it (I almost certainly need to use
> remember.el to streamline things further). Here's an example:
>
> * PROJECT [#B] submit newer expenses :@internet:admin:
> ** NEXT submit to iExpense :sub60:
Sorry to reply to my own post, but I forgot to say: having shortcuts
for assigning tags (relatively new functionality in org.el) is a GREAT
help in speeding up the categorisation process. I have this at the
end of my TODO.org:
* mode settings
:HIDE:
#+ARCHIVE: DONE.org::
#+CATEGORY: work
#+SEQ_TODO: NEXT(n) | DONE(N) | WAITING(w)
#+SEQ_TODO: PROJECT(p) | PROJDONE(P)
#+SEQ_TODO: SOMEDAY(s) MAYBE(m) | CANCELLED(c)
#+STARTUP: logdone
#+STARTUP: hidestars
#+TAGS: { @internet(i) @offline(0) @phone(p) @home(h) }
- various GTD contexts
#+TAGS: { sub10(1) sub30(3) sub60(6) sub120(2) sub4(4) subday(d) }
- rough estimates of max. time per task
#+TAGS: admin(a)
- paperwork etc.
#+TAGS: org(o)
- "sharpening the saw" - improving my self-organization process
- can overlap with computer(c) but also non-electronic organization
#+TAGS: computer(c)
- optimising the way I use it
- better config
- hacks to help workflow
[snipped work-related]
:END:
* local variables
** Local Variables: **
** org-drawers: '("PROPERTIES" "HIDE") **
** End: **
prev parent reply other threads:[~2007-09-24 23:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 20:44 GTD: Solving the bottleneck of converting incoming mails to NEXT actions Georg C. F. Greve
2007-09-24 22:26 ` John Wiegley
2007-09-25 9:45 ` Georg C. F. Greve
2007-09-25 12:52 ` Bastien
2007-09-25 14:05 ` Georg C. F. Greve
2007-09-25 15:44 ` Bastien
2007-09-25 16:08 ` Georg C. F. Greve
2007-09-25 16:29 ` Bastien
2007-09-25 17:34 ` Carsten Dominik
2007-09-25 22:24 ` Georg C. F. Greve
2007-09-25 16:07 ` Carsten Dominik
2007-09-25 17:35 ` Nuutti Kotivuori
2007-09-25 18:20 ` Carsten Dominik
2007-09-24 22:52 ` Adam Spiers
2007-09-24 23:04 ` Adam Spiers [this message]
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=20070924230459.GB9383@atlantic.linksys.moosehall \
--to=orgmode@adamspiers.org \
--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).