From: Ihor Radchenko <yantar92@posteo.net>
To: David Masterson <dsmasterson@gmail.com>
Cc: Daniel Fleischer <danflscr@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: org-todo-keywords and task sequence
Date: Tue, 17 Jan 2023 18:30:25 +0000 [thread overview]
Message-ID: <87edrtggji.fsf@localhost> (raw)
In-Reply-To: <SJ0PR03MB5455A5601A51868125D397C8A2C69@SJ0PR03MB5455.namprd03.prod.outlook.com>
David Masterson <dsmasterson@gmail.com> writes:
> The problem is (I think), when you attach @ or ! to the state and, as you
> cycle thru (S-right), new unintended notes will be added as you cycle to
> the state you're looking for. True?
If you attach @ or !, those notes are not unintended.
S-right is not for you to play around, it is for actual work on actual
tasks. If you tell Org to take a not on switching to next TODO state,
that's what you want. If you don't want it, don't put @ or !.
> Can you repeat a keyword in org-todo-keywords? Perhaps there should be a
> sparse table defining, for a current state, what are the potential next
> states? ...
No. S-right feature is there for simple workflows.
I am against introducing complex workflows for no reason.
It will do no good for the users. Complex workflows are rarely useful in
practice, except some specialized scenarios, which are not common enough
to include into the core.
And yes, you can use org-edna or custom org-trigger-hook if you need
something non-orthodox.
--
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>
next prev parent reply other threads:[~2023-01-17 18:31 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 [this message]
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=87edrtggji.fsf@localhost \
--to=yantar92@posteo.net \
--cc=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).