[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Orgmode] Re: When is a TODO really a TODO ? ...
From: |
Richard G Riley |
Subject: |
Re: [Orgmode] Re: When is a TODO really a TODO ? ... |
Date: |
Tue, 06 Nov 2007 14:25:36 +0100 |
User-agent: |
Gnus/5.110007 (No Gnus v0.7) Emacs/22.1.50.6 (gnu/linux) |
Bastien <address@hidden> writes:
> "Eddward DeVilla" <address@hidden> 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.