From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: When is a TODO really a TODO ? ... Date: Mon, 05 Nov 2007 11:21:47 -0500 Message-ID: <87abps7jdw.fsf@gollum.intra.norang.ca> References: <6E89C935-605F-46C8-8B97-63FEE2A827F5@science.uva.nl> 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 1Ip4if-0006D6-Fv for emacs-orgmode@gnu.org; Mon, 05 Nov 2007 11:22:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ip4ia-00061O-ON for emacs-orgmode@gnu.org; Mon, 05 Nov 2007 11:22:33 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ip4ia-00060z-Ko for emacs-orgmode@gnu.org; Mon, 05 Nov 2007 11:22:28 -0500 Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ip4ia-0003Kx-7H for emacs-orgmode@gnu.org; Mon, 05 Nov 2007 11:22:28 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ip4iK-0007yk-RM for emacs-orgmode@gnu.org; Mon, 05 Nov 2007 16:22:12 +0000 Received: from cpe000102d0fe75-cm0012256ecbde.cpe.net.cable.rogers.com ([99.239.148.180]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Nov 2007 16:22:12 +0000 Received: from bernt by cpe000102d0fe75-cm0012256ecbde.cpe.net.cable.rogers.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Nov 2007 16:22:12 +0000 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 Carsten Dominik writes: > you make an interesting point. The fact that items with a process > state are called TODO > items had two roots: > > - historically: Initially, there was only TODO and DONE. > > - 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 ? ,---- | * TODO Thing 1 | I'm a task | ** NEXT Thing 1 first item | Me too! work on me next | * Some random information | I'm not a task since I don't need to be 'done' | * DONE Completed task | I'm a completed task `---- Bernt