* conceptual TODO help?
@ 2012-07-28 18:04 scrawler
2012-07-28 19:05 ` Thomas S. Dye
2012-07-29 8:47 ` Eric Abrahamsen
0 siblings, 2 replies; 3+ messages in thread
From: scrawler @ 2012-07-28 18:04 UTC (permalink / raw)
To: emacs-orgmode
Hi guys, I have a few questions about todo states. I have these
keywords defined:
#+TODO: Do Doing DoBy DoLater | Did DidNot DidNever
#+TAGS: @Beverly(y) @Bionca(a)
I'd like to have a better understanding of the TODO sequence for any
given task, assignment, or project. The states Do and Did are pretty
obviously just TODO and DONE renamed. I can maybe add a
DEADLINE:<2012-07-28 Sat> for the DoBy heading, and a
SCHEDULED:<2012-07-28 Sat> for DoLater, but what can or should I do
with Doing? Should I just leave it alone and look at it?
I think I've seen TODO keywords defined (in the manual? list emails?)
like "feedback", etc, but it seems like if I have a basic but
comprehensive sequence I can put that kind of stuff in tags
(Incidentally, what are the @ signs in front of tags for?).
Are there any keywords I should add or remove? Should I get rid of
DidNot and DidNever (implying not yet and never will)? My keywords are
arbitrary and silly, but I'd like to better understand the states they
label.
Thanks, I hope I was clear, and sorry for the "basic question" noise.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: conceptual TODO help?
2012-07-28 18:04 conceptual TODO help? scrawler
@ 2012-07-28 19:05 ` Thomas S. Dye
2012-07-29 8:47 ` Eric Abrahamsen
1 sibling, 0 replies; 3+ messages in thread
From: Thomas S. Dye @ 2012-07-28 19:05 UTC (permalink / raw)
To: scrawler; +Cc: emacs-orgmode
Aloha scrawler,
scrawler <scrawler@gmail.com> writes:
> Hi guys, I have a few questions about todo states. I have these
> keywords defined:
>
> #+TODO: Do Doing DoBy DoLater | Did DidNot DidNever
> #+TAGS: @Beverly(y) @Bionca(a)
>
> I'd like to have a better understanding of the TODO sequence for any
> given task, assignment, or project. The states Do and Did are pretty
> obviously just TODO and DONE renamed. I can maybe add a
> DEADLINE:<2012-07-28 Sat> for the DoBy heading, and a
> SCHEDULED:<2012-07-28 Sat> for DoLater, but what can or should I do
> with Doing? Should I just leave it alone and look at it?
I found the discussions of TODO states by John Wiegley, Charles Cave,
and Bernt Hansen very helpful: http://orgmode.org/worg/org-tutorials/index.html#sec-2
I eventually set up my files along the lines laid out by Bernt, but I
don't track things as exhaustively as he's able to do.
hth,
Tom
>
> I think I've seen TODO keywords defined (in the manual? list emails?)
> like "feedback", etc, but it seems like if I have a basic but
> comprehensive sequence I can put that kind of stuff in tags
> (Incidentally, what are the @ signs in front of tags for?).
>
> Are there any keywords I should add or remove? Should I get rid of
> DidNot and DidNever (implying not yet and never will)? My keywords are
> arbitrary and silly, but I'd like to better understand the states they
> label.
>
> Thanks, I hope I was clear, and sorry for the "basic question" noise.
>
>
--
Thomas S. Dye
http://www.tsdye.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: conceptual TODO help?
2012-07-28 18:04 conceptual TODO help? scrawler
2012-07-28 19:05 ` Thomas S. Dye
@ 2012-07-29 8:47 ` Eric Abrahamsen
1 sibling, 0 replies; 3+ messages in thread
From: Eric Abrahamsen @ 2012-07-29 8:47 UTC (permalink / raw)
To: emacs-orgmode
On Sun, Jul 29 2012, scrawler wrote:
> Hi guys, I have a few questions about todo states. I have these
> keywords defined:
>
> #+TODO: Do Doing DoBy DoLater | Did DidNot DidNever
> #+TAGS: @Beverly(y) @Bionca(a)
>
> I'd like to have a better understanding of the TODO sequence for any
> given task, assignment, or project. The states Do and Did are pretty
> obviously just TODO and DONE renamed. I can maybe add a
> DEADLINE:<2012-07-28 Sat> for the DoBy heading, and a
> SCHEDULED:<2012-07-28 Sat> for DoLater, but what can or should I do
> with Doing? Should I just leave it alone and look at it?
>
> I think I've seen TODO keywords defined (in the manual? list emails?)
> like "feedback", etc, but it seems like if I have a basic but
> comprehensive sequence I can put that kind of stuff in tags
> (Incidentally, what are the @ signs in front of tags for?).
>
> Are there any keywords I should add or remove? Should I get rid of
> DidNot and DidNever (implying not yet and never will)? My keywords are
> arbitrary and silly, but I'd like to better understand the states they
> label.
Some things to consider:
Say you use DEADLINE for DoBy and SCHEDULED for DoLater: now, does a
DoBy or DoLater tag carry any more information than a "Do plus SCHEDULED
property" or a "Do plus DEADLINE property"? You might think they'll be
easier to search for, but what if you have a DoLater and forget to add a
SCHEDULED? I tend to go for the minimum amount of significant
information, and avoid duplication.
What's the difference between a DidNot and a Do? Or DidNot and a Doing,
for that matter?
I've got a CANCELLED(c@), which would be the same thing as your
DidNever, except that the @ means I have to add an explanation for *why*
it's canceled, and that's useful for record-keeping.
I think @ in tags is a convention for indicating a "location" category,
like @home or @office. I may be wrong, but I think it has no effect
whatsoever on Org's treatment of the tag.
Hope that's good for something…
Definitely second Thomas' link to the online docs…
Eric
--
GNU Emacs 24.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.24.11)
of 2012-07-23 on pellet
7.8.11
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-07-29 8:48 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-28 18:04 conceptual TODO help? scrawler
2012-07-28 19:05 ` Thomas S. Dye
2012-07-29 8:47 ` Eric Abrahamsen
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).