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 03:28:24 +0000 [thread overview]
Message-ID: <87hck0833b.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87abps7jdw.fsf@gollum.intra.norang.ca> (Bernt Hansen's message of "Mon, 05 Nov 2007 11:21:47 -0500")
Bernt Hansen <bernt@alumni.uwaterloo.ca> writes:
>> - pedagogically: Org-mode tries to be "easy-entry, but then
>> lots of stuff under the hood".
>> This is why TODO items are introduced the way they are.
>> You said that you have been confused by this, so maybe it
>> is not the right way after all. Any proposals on how to
>> address this in the docs?
>>
>
> Maybe just call todo items 'Tasks' and their current state is 'TODO',
> 'DONE', etc ?
Good idea. Here is a list of possible conventions for the manual:
- use "keyword" for TODO keyword
- use "tasks" for entries that have a keyword
- use "entries" for other entries (or entries "in general")
- use "heading" when referring to the entry as "outline-able"
- use "headline" in the context of exporting/publishing
Maybe some typesetting conventions wouldn't hurt, too:
- use uppercase for KEYWORD
- use uppercase for drawers and special PROPERTIES
- capitalized the first letter for user-defined properties
- use lower-case for tags
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?
--
Bastien
next prev parent reply other threads:[~2007-11-06 2:28 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 [this message]
2007-11-06 5:46 ` Carsten Dominik
[not found] ` <b71b18520711051926x27263459h885ff55e57f27664@mail.gmail.com>
2007-11-06 14:06 ` Bastien
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=87hck0833b.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).