From: Carsten Dominik <dominik@science.uva.nl>
To: Wanrong Lin <wanrong.lin@gmail.com>
Cc: org-mode list <emacs-orgmode@gnu.org>
Subject: Re: Definition of "unscheduled" task
Date: Tue, 16 Oct 2007 08:49:57 +0200 [thread overview]
Message-ID: <2706d3f0ffce5163033e68529d552912@science.uva.nl> (raw)
In-Reply-To: <4713BAA3.1070702@gmail.com>
On Oct 15, 2007, at 21:08, Wanrong Lin wrote:
>
> Sounds like my argument did not convince you. :-)
No, you misunderstand. I do see why you might want to mark
appointments TODO (even if I would not do it). But
"scheduled" in the context of Org has to do with *planning*.
You *plan* to work on this item that day, but it is not ab
absolute fix like a dentist appointment. So I think it
is wrong to turn these off with a variable that contains the
word "scheduled" in the name.
- Carsten
> But a new variable works for me. I really appreciate the extra effort
> you take.
>
> Wanrong
>
> Carsten Dominik wrote:
>> Well,
>>
>> I am not about the change the meaning of "scheduled", but I can give
>> you a new
>> variable `org-agenda-todo-ignore-with-date'. How about that?
>>
>> - Carsten
>>
>> On Oct 14, 2007, at 17:45, Wanrong Lin wrote:
>>
>>>
>>> That's certainly an option. But usually I like to mark any
>>> "actionable" items with "TODO", while using non-TODO entries to
>>> record information, or to group TODOs into logical groups. Like
>>> this:
>>>
>>> * Dental
>>> *** TODO See Dr. Xyz for cleaning
>>> <2007-11-29 Thu 09:00>
>>> * Medical
>>> *** TODO See Dr. Abc for routine exam
>>> * Useful Websites
>>>
>>> Conceptually, I think it is cleaner that way (if the entry
>>> indicates some action, have a "TODO" keyword. How that action is
>>> scheduled is a separate issue.). Physiologically, If I know in my
>>> org system certain entries need action but don't have a TODO
>>> keyword, my trust of the system will decrease since there are many
>>> functions in org-mode that operates on TODO entries only (or better
>>> so). Also, with a TODO keyword, I can change the state of it (I can
>>> cancel it, I can mark it done and etc.). Further, sometimes you just
>>> want to create a TODO entry like "See Dr. Abc", and later make it an
>>> appointment by adding a time stamp. It seems awkward to me that I
>>> need to remove the "TODO" keyword once I have that item scheduled as
>>> an appointment.
>>>
>>> In short, I think we should mark appointments as "TODO" entries and
>>> have appointments removed from the TODO item list if
>>> "ignore-scheduled" is turned on.
>>>
>>> Wanrong
>>>
>>> Carsten Dominik wrote:
>>>>
>>>> On Oct 14, 2007, at 5:35, Wanrong Lin wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am trying to follow GTD's principle that tasks should be
>>>>> reviewed regularly. So I first turn on
>>>>> "org-agenda-todo-ignore-scheduled", and do a "List of all TODO
>>>>> entries, and then review all tasks in the list. However, I found
>>>>> that tasks with plain active time stamps ("appointment tasks") are
>>>>> also listed. Should we exclude them when
>>>>> org-agenda-todo-ignore-scheduled is set to "t"?
>>>>
>>>> Wouldn't it be better to not mark appointments TODO?
>>>>
>>>> - Carsten
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Emacs-orgmode mailing list
>>> Remember: use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>
>>>
>>
>> --
>> Carsten Dominik
>> Sterrenkundig Instituut "Anton Pannekoek"
>> Universiteit van Amsterdam
>> Kruislaan 403
>> NL-1098SJ Amsterdam
>> phone: +31 20 525 7477
>>
>
>
--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477
prev parent reply other threads:[~2007-10-16 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 3:35 Definition of "unscheduled" task Wanrong Lin
2007-10-14 6:17 ` Carsten Dominik
2007-10-14 15:45 ` Wanrong Lin
2007-10-15 18:45 ` Carsten Dominik
2007-10-15 19:08 ` Wanrong Lin
2007-10-16 6:49 ` Carsten Dominik [this message]
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=2706d3f0ffce5163033e68529d552912@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=wanrong.lin@gmail.com \
/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).