emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Brand <michael.ch.brand@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Can't use char ">" in TODO state
Date: Tue, 18 Oct 2011 13:25:52 +0200	[thread overview]
Message-ID: <CALn3zoimMChdNL0MBpsFVYziCsqiutPXkzwJ=uZKf3i-XqgCYA@mail.gmail.com> (raw)
In-Reply-To: <80d3duoajd.fsf@somewhere.org>

Hi Sebastien

On Tue, Oct 18, 2011 at 12:32, Sebastien Vauban
> Instead of using the TODO state "NEW", I tried using "NEW>" so that it
> occupies 4 letters, as all my other states (better display in the agenda).
> Though...
> * TEST Do this
> Simply use S-right arrow to cycle through the different states, and you'll see
> "NEW>" added many times:
> - DONE Do this
> - CANX Do this
> - Do this
> - NEW> Do this
>  which "prooves" that "NEW>" is well somehow considered as a TODO state,
>  being added automagically, but the next cycle steps don't succeed...
> - NEW> NEW> Do this
> - NEW> NEW> NEW> Do this
> - ...
> 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 ...

It works with this patch
from Nicolas which I am still using to test it.

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

What about NEVV ?  (ok, it was a joke)


  reply	other threads:[~2011-10-18 11:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 10:32 Can't use char ">" in TODO state Sebastien Vauban
2011-10-18 11:25 ` Michael Brand [this message]
2011-10-21 15:11   ` Bastien
2011-10-23  7:38     ` Nicolas Goaziou
2011-10-23 15:07       ` Jambunathan K
2011-10-23 16:19         ` Nicolas Goaziou
2011-10-23 18:07       ` Bastien
2011-10-24  9:22       ` Sebastien Vauban
2011-10-26 16:51         ` Sebastien Vauban
2011-10-21 15:07 ` Bastien

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:

  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='CALn3zoimMChdNL0MBpsFVYziCsqiutPXkzwJ=uZKf3i-XqgCYA@mail.gmail.com' \
    --to=michael.ch.brand@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=wxhgmqzgwmuf@spammotel.com \


* 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


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).