From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@altern.org>
Subject: Re: Can't use char ">" in TODO state
Date: Fri, 21 Oct 2011 17:07:39 +0200
Message-ID: <87k47ys50i.fsf@altern.org>
References: <80d3duoajd.fsf@somewhere.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:38361)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1RHHbk-0004pr-AV
	for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 12:06:13 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1RHHbe-00035P-JA
	for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 12:06:08 -0400
Received: from mail-wy0-f169.google.com ([74.125.82.169]:41860)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1RHHbe-00034B-Dd
	for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 12:06:02 -0400
Received: by mail-wy0-f169.google.com with SMTP id 34so4942847wyg.0
	for <emacs-orgmode@gnu.org>; Fri, 21 Oct 2011 09:06:02 -0700 (PDT)
In-Reply-To: <80d3duoajd.fsf@somewhere.org> (Sebastien Vauban's message of
	"Tue, 18 Oct 2011 12:32:06 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org

Hi Sébastien,

"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:

> I find this behavior not entirely satisfying, even if I can fully accept that
> ">" is a forbidden character in the TODO states. For example, we could think
> of a warning being generated, or of the state being fully ignored, or ...

I agree there is inconsistency here.  Special chars are allowed in TODO
keywords but they create the confusion you describe when used at the beg
or the end of the keyword ("NE>W" is safe AFAICT.)

> BTW, do you have an alternative for this "NEW" state, in 4 positions?
> ;-)

NIOU?

:)

-- 
 Bastien