emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: David Masterson <dsmasterson@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-todo-keywords and task sequence
Date: Tue, 17 Jan 2023 10:56:32 +0000	[thread overview]
Message-ID: <871qntig4f.fsf@localhost> (raw)
In-Reply-To: <SJ0PR03MB545535D154CF21FD72347704A2C69@SJ0PR03MB5455.namprd03.prod.outlook.com>

David Masterson <dsmasterson@gmail.com> writes:

> I'm not sure I understand 'sequence' and 'type' in org-todo-keywords.
> In particular, I can only think of the following simple sequence as
> being possible in org-todo-keywords:
>
> TODO -> IN-PROCESS -> DONE
>
> If I want to add in (say) WAITING, the graph (represented as a table)
> becomes:
>
> i\o  | TODO | IN-P | WAIT | DONE
> TODO |  N   |  Y   |  N   |  N
> IN-P |  N   |  N   |  Y   |  Y
> WAIT |  N   |  Y   |  N   |  N
> DONE |  N   |  N   |  N   |  N

The main purpose of the keyword sequences is working on tasks in steps.
When a keyword is a part of sequence, you can just use S-<right>
S-<left> to progress the task. For example:

NEXT -> DOING -> REVIEW -> DONE 

Such sequence is only making sense when everything goes "as usual" with
a task and you do not want to think about which keyword to assign.

The transition IN-PROGRESS -> WAIT is something you have to decide
consciously. Org cannot just read you mind and change IN-PROGRESS to
WAIT. You will have set such transition manually.

For your table, you can try something like

#+TODO: WAIT IN-PROCESS
#+TODO: TODO IN-PROCESS | DONE

Note, however, that moving S-<left> will be ambiguous.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  parent reply	other threads:[~2023-01-17 10:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17  6:10 org-todo-keywords and task sequence David Masterson
2023-01-17  8:10 ` Daniel Fleischer
2023-01-17  8:17   ` Daniel Fleischer
2023-01-17 18:08     ` David Masterson
2023-01-17 18:30       ` Ihor Radchenko
2023-01-18  1:59         ` David Masterson
2023-01-18  2:17         ` David Masterson
2023-01-18 11:04           ` Ihor Radchenko
2023-01-17 10:56 ` Ihor Radchenko [this message]
2023-01-17 18:13   ` David Masterson
2023-01-17 18:32     ` Ihor Radchenko
2023-01-18  2:07       ` David Masterson
2023-01-18 11:06         ` Ihor Radchenko

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=871qntig4f.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=dsmasterson@gmail.com \
    --cc=emacs-orgmode@gnu.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).