From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bernt Hansen <bernt@alumni.uwaterloo.ca>
Subject: Re: Org-mode Version 5.07
Date: Thu, 30 Aug 2007 09:26:08 -0400
Message-ID: <87fy21i26n.fsf@gollum.intra.norang.ca>
References: <2ae851ed8680bed6915861cb29420016@science.uva.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IQk2J-0005pB-B3
	for emacs-orgmode@gnu.org; Thu, 30 Aug 2007 09:26:15 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IQk2G-0005nk-SH
	for emacs-orgmode@gnu.org; Thu, 30 Aug 2007 09:26:14 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IQk2G-0005nV-Pi
	for emacs-orgmode@gnu.org; Thu, 30 Aug 2007 09:26:12 -0400
Received: from outbound.mailhop.org ([63.208.196.171])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <bernt@norang.ca>) id 1IQk2G-0000yg-64
	for emacs-orgmode@gnu.org; Thu, 30 Aug 2007 09:26:12 -0400
In-Reply-To: <2ae851ed8680bed6915861cb29420016@science.uva.nl> (Carsten
	Dominik's message of "Thu\, 30 Aug 2007 11\:52\:23 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Carsten Dominik <dominik@science.uva.nl>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>

Carsten Dominik <dominik@science.uva.nl> writes:

>   - Some People use TODO states more like tags.  For them the
>     TODO keywords mark special states and they like to quickly
>     switch between states in arbitrary sequence.  The standard
>     TODO interface is not perfect for this, because it assumes
>     that the states are reached in sequence.  However, the fast
>     tag setting interface is in fact perfect for this.  You can
>     now "misuse" the TAG selection interface to also set TODO
>     states.  All you need to do is to assign keys to the TODO
>     states, just like you also do for tags.
>
>      #+SEQ_TODO: TODO(t) WAITING(w) | CANCELED(c) DONE(d)
>      #+TAGS: @HOME(h) @OFFICE(o) @SHOP(s)
>
>     Next time you try to set tags with C-c C-c, the todo states
>     will be offered as well, and the corresponding key will
>     switch the entry to that state.

This is a great idea... except the DONE(d) entry messes up the agenda
view => DONE tasks appear in the agenda again.

Bernt