emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: "Sébastien Vauban"
	<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: Suggestions needed for handling "ideas"
Date: Tue, 27 Apr 2010 21:59:21 -0400	[thread overview]
Message-ID: <87och4s5fq.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87zl0pqke3.fsf@mundaneum.com> ("Sébastien Vauban"'s message of "Tue\, 27 Apr 2010 12\:07\:00 +0200")



Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
writes:

> I really am puzzled by using a "TODO state" for saying "this is a note".
>
> For me, a so-called TODO state is a circumstance (or a mode), so one
> transitional property on a cycle. That's something that evolves over time,
> such as:
>
>     TODO -> NEXT -> STARTED -> WAITING -> DONE
>
> A NOTE does not belong to such cycles. It's just some kind of "property".
>
> I would be more inclined to view a NOTE "property" as a tag, but that does not
> satisfy me neither. Tags are for contexts, mainly resources we need to have at
> hand, or locations we need to be, or time ranges in which the action makes
> sense.

I think that's too narrow a view for tags.  Tags should be whatever is
useful.  It can be a context, or resources you need, or locations, or
anything else that is useful.

I use arbitrary tags to match items with an external tracking system -
and use the id of that system so I can match them easily.  I also
use :NOTE: for notes.  It works for my needs just fine.  Tags are not
and should not be limited to context only.  I also use tags for special
todo states... if I cancel a task I give it a CANCELLED tag too ... so
any subtask of the cancelled task is obviously cancelled and unavailable
to work on.

-Bernt

  reply	other threads:[~2010-04-28  1:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 19:46 Suggestions needed for handling "ideas" Ali Tofigh
2010-04-12 20:38 ` John Hendy
2010-04-12 21:04   ` Ali Tofigh
2010-04-25  7:46 ` John Wiegley
2010-04-26 14:47   ` Ali Tofigh
2010-04-26 17:00     ` Matt Lundin
2010-04-26 17:30       ` Ali Tofigh
2010-05-20  0:14       ` Ali Tofigh
2010-04-27 10:07     ` Sébastien Vauban
2010-04-28  1:59       ` Bernt Hansen [this message]
2010-04-26 16:16   ` Nathan Neff

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=87och4s5fq.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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).