From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: Chao LU <loochao@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Multi Todo state
Date: Tue, 07 Dec 2010 15:22:53 +0000 [thread overview]
Message-ID: <87fwu9edcw.fsf@ucl.ac.uk> (raw)
In-Reply-To: AANLkTikP559gsUy4=gjN_2Zaov0d4Sx22QzzLjroRxHW@mail.gmail.com
suvayu ali <fatkasuvayu+linux@gmail.com> writes:
> Hi Chao,
>
> On Tue, Dec 7, 2010 at 8:54 AM, Chao LU <loochao@gmail.com> wrote:
>> Besides, what's the essential difference between TODO and TAG? Since to me,
>> TODO is kind of special TAG?
>>
>
> The way I understand it, TODO states have a flow/sequence to it.
> Although they need not always be sequential, e.g. a type TODO keyword,
> still they have a flow of NOTDONE --> DONE associated with them.
> Whereas, a tag is probably more of a concept related to filing or
> categorising and don't as such represent a work flow of any kind.
and, for the OP, don't forget that there are two other pieces of
information associated with any item: a CATEGORY and the file name.
This gives a total of 4 data that can be used to /label/ items of
interest, not counting the headline itself, of course.
Agenda views will easily display 3 of the 4 data (default is category,
todo state and tags, IRC).
I use categories for projects, tags for individuals and TODO states for
state information.
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 23.2.1
: using Org-mode version 7.3 (release_7.3.221.gb3e16)
next prev parent reply other threads:[~2010-12-07 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 7:54 Multi Todo state Chao LU
2010-12-07 8:02 ` suvayu ali
2010-12-07 15:22 ` Eric S Fraga [this message]
2010-12-07 19:26 ` Elsevier's "Executable Paper Grand Challenge" Bill White
2010-12-07 21:02 ` Thomas S. Dye
2010-12-07 21:09 ` Erik Iverson
2010-12-09 9:24 ` Joost Helberg
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=87fwu9edcw.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.com \
--cc=loochao@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).