From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: When is a TODO really a TODO ? ... Date: Tue, 06 Nov 2007 03:28:24 +0000 Message-ID: <87hck0833b.fsf@bzg.ath.cx> References: <6E89C935-605F-46C8-8B97-63FEE2A827F5@science.uva.nl> <87abps7jdw.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IpEB8-0007SF-UR for emacs-orgmode@gnu.org; Mon, 05 Nov 2007 21:28:34 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IpEB8-0007Re-CL for emacs-orgmode@gnu.org; Mon, 05 Nov 2007 21:28:34 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IpEB8-0007RW-8k for emacs-orgmode@gnu.org; Mon, 05 Nov 2007 21:28:34 -0500 Received: from hu-out-0506.google.com ([72.14.214.224]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IpEB8-0001D2-0U for emacs-orgmode@gnu.org; Mon, 05 Nov 2007 21:28:34 -0500 Received: by hu-out-0506.google.com with SMTP id 23so828883huc for ; Mon, 05 Nov 2007 18:28:32 -0800 (PST) In-Reply-To: <87abps7jdw.fsf@gollum.intra.norang.ca> (Bernt Hansen's message of "Mon, 05 Nov 2007 11:21:47 -0500") 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: emacs-orgmode@gnu.org 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? -- Bastien