From: David Masterson <dsmasterson@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Daniel Fleischer <danflscr@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: org-todo-keywords and task sequence
Date: Tue, 17 Jan 2023 17:59:44 -0800 [thread overview]
Message-ID: <SJ0PR03MB545572E771F6954AFE1248B4A2C79@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <87edrtggji.fsf@localhost> (Ihor Radchenko's message of "Tue, 17 Jan 2023 18:30:25 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> 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 note on switching to next TODO state,
> that's what you want. If you don't want it, don't put @ or !.
Or cycling -- note taking is much more important and cycling only works
for simple workflows. My previous example shows how easy it is to make
a (by Org definition) "complex" workflow. I could probably use tags for
changing states, but notes are not automatic. And you're using two
things for essentially the same purpose (state transition).
>> 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.
If org-todo-keywords has no sequence, does S-right cycle? I suppose I
could shift to just types and tags and avoid S-right.
Workflows can easily get complex -- just add WAIT and HOLD for example.
> And yes, you can use org-edna or custom org-trigger-hook if you need
> something non-orthodox.
I'll have to explore org-edna more. I do think that the use of
"sequence" in org-todo-keywords complicates the variable because it
talks about "simple workflow" and leaves people wondering (like me) how
to change their view of a workflow to fit Org.
I'll play with it some more.
--
David Masterson
next prev parent reply other threads:[~2023-01-18 2:05 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 [this message]
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=SJ0PR03MB545572E771F6954AFE1248B4A2C79@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson@gmail.com \
--cc=danflscr@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).