From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard G Riley Subject: Re: Re: When is a TODO really a TODO ? ... Date: Tue, 06 Nov 2007 14:25:36 +0100 Message-ID: References: <6E89C935-605F-46C8-8B97-63FEE2A827F5@science.uva.nl> <87abps7jdw.fsf@gollum.intra.norang.ca> <87hck0833b.fsf@bzg.ath.cx> <87d4un8o50.fsf@bzg.ath.cx> 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 1IpOR7-0003X5-PQ for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 08:25:45 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IpOR4-0003Tm-Es for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 08:25:45 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IpOR4-0003Tf-Av for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 08:25:42 -0500 Received: from mu-out-0910.google.com ([209.85.134.189]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IpOR3-0006tp-VO for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 08:25:42 -0500 Received: by mu-out-0910.google.com with SMTP id i2so3483257mue for ; Tue, 06 Nov 2007 05:25:40 -0800 (PST) In-Reply-To: <87d4un8o50.fsf@bzg.ath.cx> (Bastien's message of "Tue\, 06 Nov 2007 14\:06\:03 +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: Bastien Cc: emacs-orgmode@gnu.org Bastien writes: > "Eddward DeVilla" writes: > >>> 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? >> >> What about if a task is not a task? What if it's a person, a >> reservation, an event or some other thing to be organized? "to be organized" - implying "task" to be undertaken. > > The purpose of "task" was to find a replacement for "TODO item". > > There are many occurrences of "TODO item" or "TODO entry" in the manual, > and "task" is better because it's more general. I agree. A task is an org-item with a status applied from a sequence of task statuses. tasks generally progress from an initial state to a completion state > > Of course it is not perfect, and no replacement would be, because it is > impossible to capture all possible uses for an entry in a single word... > but in the lack of better alternatives, I think it's okay, especially if > we dedicate a "Writing conventions" section at the beginning of the > manual, explaining both the scope and the limitation of conventions > (like using "tasks" for headlines that have a keyword). > >> We need to make sure we keep is easy cases easy. I don't think >> incremental discoveries after that are a bad thing. > > Yes, precisely. This is why all these possible conventions have to be > carefully and gradually implemented, so that we can check new Org users > don't get lost.