From: Rene <jlr_0@yahoo.com>
To: emacs-orgmode@gnu.org
Subject: Re: Is OrgMode really GTD compliant?
Date: Mon, 28 Apr 2014 17:18:53 +0000 (UTC) [thread overview]
Message-ID: <loom.20140428T190134-14@post.gmane.org> (raw)
In-Reply-To: 87wqeaqp5t.fsf@berkeley.edu
Richard Lawrence <richard.lawrence <at> berkeley.edu> writes:
> I am not really familiar with the official GTD methodology, and I don't
> know exactly how you would normally represent the "energy needed"
> associated with a task, but here's a suggestion.
>
> It occurs to me that you could just use the A/B/C priority cookies to
> represent energy levels, since you don't want to use them to encode
> priorities. Something like:
> #A: need to be fresh
> #C: can be wasted
> #B: everything else
> or whatever would work for you. If that's granular enough to represent
> your energy-needed levels, then it's a neat hack that requires zero
> customization. Sorting and filtering by energy needed is then already
> built into the agenda functions, etc. Just think "energy needed"
> whenever Org says "priority" (which isn't very often), and you're good
> to go.
That's exactly what I've been doing so far. But that's not that convenient.
The energy level appears in front of the action headline. This adds noise
to the real action info.
I think I'll have to make the "Energy Level" an orgmode property that
appears in the :PROPERTIES: drawer of the action.
I'm not used to defining new properties in orgmode. I'll try to define an
"Energy" property as well as functions like "org-agenda-cmp-user-defined" in
order to correctly use "org-agenda-sorting-strategy", unless someone has
already done so...
--
next prev parent reply other threads:[~2014-04-28 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 20:51 Is OrgMode really GTD compliant? Rene
2014-04-28 0:21 ` Richard Lawrence
2014-04-28 17:18 ` Rene [this message]
2014-04-29 6:51 ` Alan Schmitt
2014-04-29 10:30 ` Samuel Loury
2014-04-29 10:49 ` Alan Schmitt
2014-04-29 13:26 ` Samuel Loury
2014-04-29 13:31 ` Bastien
2014-04-29 13:37 ` Alan Schmitt
2014-04-29 13:42 ` 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=loom.20140428T190134-14@post.gmane.org \
--to=jlr_0@yahoo.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).