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 14:06:03 +0000 Message-ID: <87d4un8o50.fsf@bzg.ath.cx> References: <6E89C935-605F-46C8-8B97-63FEE2A827F5@science.uva.nl> <87abps7jdw.fsf@gollum.intra.norang.ca> <87hck0833b.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 1IpO8N-0006LZ-R4 for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 08:06:23 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IpO8M-0006L1-7W for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 08:06:23 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IpO8M-0006Ky-4J for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 08:06:22 -0500 Received: from fk-out-0910.google.com ([209.85.128.187]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IpO8L-0001Pd-JF for emacs-orgmode@gnu.org; Tue, 06 Nov 2007 08:06:21 -0500 Received: by fk-out-0910.google.com with SMTP id 19so3984077fkr for ; Tue, 06 Nov 2007 05:06:20 -0800 (PST) In-Reply-To: (Eddward DeVilla's message of "Mon, 5 Nov 2007 21:26:20 -0600") 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 "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? 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. 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. -- Bastien