From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rene Subject: Re: Is OrgMode really GTD compliant? Date: Mon, 28 Apr 2014 17:18:53 +0000 (UTC) Message-ID: References: <87wqeaqp5t.fsf@berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33014) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WepCy-0007S5-9m for emacs-orgmode@gnu.org; Mon, 28 Apr 2014 13:19:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WepCs-0005c2-Ph for emacs-orgmode@gnu.org; Mon, 28 Apr 2014 13:19:12 -0400 Received: from plane.gmane.org ([80.91.229.3]:42284) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WepCs-0005bt-IF for emacs-orgmode@gnu.org; Mon, 28 Apr 2014 13:19:06 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WepCq-0006qQ-CP for emacs-orgmode@gnu.org; Mon, 28 Apr 2014 19:19:04 +0200 Received: from LLagny-156-34-52-217.w80-13.abo.wanadoo.fr ([80.13.159.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 28 Apr 2014 19:19:04 +0200 Received: from jlr_0 by LLagny-156-34-52-217.w80-13.abo.wanadoo.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 28 Apr 2014 19:19:04 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Richard Lawrence 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... --