emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniel Fleischer <danflscr@gmail.com>
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:10:40 +0200	[thread overview]
Message-ID: <m2o7qxbmyn.fsf@gmail.com> (raw)
In-Reply-To: <SJ0PR03MB545535D154CF21FD72347704A2C69@SJ0PR03MB5455.namprd03.prod.outlook.com> (David Masterson's message of "Mon, 16 Jan 2023 22:10:22 -0800")

David Masterson <dsmasterson@gmail.com> writes:

> I'm not sure I understand 'sequence' and 'type' in org-todo-keywords.

You're over thinking it. You can define various todo keywords and they
are divided into two groups that can be thought of as "ones that need
your attention" and "ones that don't need your attention" and they are
separated by a literal "|". Example: todo, in progress, on hold,
waiting, phonecall etc are of the 1st type. Done, canceled, postponed are of the
2nd type. In terms of "moving" between them, it's either cyclical or you
can jump to a specific word using shortcuts you define e.g.

#+TODO: TODO(t) | DONE(d)

Don't let the cyclical switching dictates the meaning, it's just an
implementation detail, done for simplicity. Hope it helped.

-- 
Daniel Fleischer


  reply	other threads:[~2023-01-17  8:11 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 [this message]
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
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=m2o7qxbmyn.fsf@gmail.com \
    --to=danflscr@gmail.com \
    --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).