From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: When is a TODO really a TODO ? ... Date: Tue, 6 Nov 2007 06:46:43 +0100 Message-ID: References: <6E89C935-605F-46C8-8B97-63FEE2A827F5@science.uva.nl> <87abps7jdw.fsf@gollum.intra.norang.ca> <87hck0833b.fsf@bzg.ath.cx> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IpIHK-0004it-2W for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 01:51:14 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IpIHI-0004hc-HR for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 01:51:13 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IpIHI-0004hY-8Y for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 01:51:12 -0500 Received: from ug-out-1314.google.com ([66.249.92.172]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IpIHI-00013L-18 for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 01:51:12 -0500 Received: by ug-out-1314.google.com with SMTP id a2so1160608ugf for ; Mon, 05 Nov 2007 22:51:11 -0800 (PST) In-Reply-To: <87hck0833b.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org On 6Nov2007, at 4:28 AM, Bastien wrote: > Bernt Hansen writes: > >>> - pedagogically: Org-mode tries to be "easy-entry, but then >>> lots of stuff under the hood". >>> This is why TODO items are introduced the way they are. >>> You said that you have been confused by this, so maybe it >>> is not the right way after all. Any proposals on how to >>> address this in the docs? >>> >> >> Maybe just call todo items 'Tasks' and their current state is 'TODO', >> 'DONE', etc ? > > Good idea. Here is a list of possible conventions for the manual: > - use "keyword" for TODO keyword > - use "tasks" for entries that have a keyword > - use "entries" for other entries (or entries "in general") > - use "heading" when referring to the entry as "outline-able" > - use "headline" in the context of exporting/publishing > > Maybe some typesetting conventions wouldn't hurt, too: > > - use uppercase for KEYWORD > - use uppercase for drawers and special PROPERTIES > - capitalized the first letter for user-defined properties > - use lower-case for tags > > Maybe this would help make the examples even more clearer. This is > especially crucial when if comes to complex agenda searches. > > What do you think? This sounds like exactly how things should be...... One possible hickup: In a GTD setting, an entry becomes a task by attaching a context, so possibly without a TODO keyword. - Carsten