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: Habits default on first STATE when rescheduled
Date: Mon, 20 Dec 2010 11:20:48 -0500	[thread overview]
Message-ID: <87ei9cct5r.fsf@norang.ca> (raw)
In-Reply-To: <80wrn4fqxe.fsf@missioncriticalit.com> ("Sébastien Vauban"'s message of "Mon, 20 Dec 2010 15:40:45 +0100")



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

> Having the following possible states:
>
> #+begin_src emacs-lisp
>   (setq org-todo-keywords
>         '((sequence "NEW(n!)"
>                     "TODO(t!)"
>                     "WAIT(w!)"
>                     "DLGT(l!)"
>                     "|"
>                     "DONE(d!)"
>                     "DFRD(f!)"
>                     "CANX(c!)")))
> #+end_src
>
> the habits, when DONE, go back to state NEW, instead of TODO. Of course, there
> is no way for Org to know it has to re-begin at the second state (in this
> case).
>
> Maybe it'd be good to add an index for habit cycles, or so?
>
> The other alternative is to put NEW after TODO, but this is quite meaningless,
> for all the other non-habit tasks that would be first TODO, then NEW, then...
> when cycling with S-arrow.

Hi Seb,

You can add a property to your habits

  :REPEAT_TO_STATE: TODO

which forces this state for repeating tasks when the item is marked DONE

HTH,
Bernt

  reply	other threads:[~2010-12-20 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 14:40 Habits default on first STATE when rescheduled Sébastien Vauban
2010-12-20 16:20 ` Bernt Hansen [this message]
2010-12-20 16:38 ` Matt Lundin
2010-12-20 20:56   ` Sébastien Vauban

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=87ei9cct5r.fsf@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).