From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: When is a TODO really a TODO ? ...
Date: Tue, 06 Nov 2007 14:06:03 +0000 [thread overview]
Message-ID: <87d4un8o50.fsf@bzg.ath.cx> (raw)
In-Reply-To: <b71b18520711051926x27263459h885ff55e57f27664@mail.gmail.com> (Eddward DeVilla's message of "Mon, 5 Nov 2007 21:26:20 -0600")
"Eddward DeVilla" <eddward@gmail.com> 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
next prev parent reply other threads:[~2007-11-06 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 17:38 When is a TODO really a TODO ? Richard G Riley
2007-11-05 6:50 ` Carsten Dominik
2007-11-05 16:21 ` Bernt Hansen
2007-11-06 3:28 ` Bastien
2007-11-06 5:46 ` Carsten Dominik
[not found] ` <b71b18520711051926x27263459h885ff55e57f27664@mail.gmail.com>
2007-11-06 14:06 ` Bastien [this message]
2007-11-06 13:25 ` Richard G Riley
2007-11-06 14:47 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d4un8o50.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).