From: David Masterson <dsmasterson@gmail.com>
To: Daniel Fleischer <danflscr@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-todo-keywords and task sequence
Date: Tue, 17 Jan 2023 10:08:08 -0800 [thread overview]
Message-ID: <SJ0PR03MB5455A5601A51868125D397C8A2C69@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <m2h6wpbmnn.fsf@gmail.com> (Daniel Fleischer's message of "Tue, 17 Jan 2023 10:17:16 +0200")
Daniel Fleischer <danflscr@gmail.com> writes:
> Daniel Fleischer [2023-01-17 Tue 10:10] wrote:
>
>> Don't let the cyclical switching dictates the meaning, it's just an
>> implementation detail, done for simplicity. Hope it helped.
>
> Put another way, if you define A B | C D E
>
> and the UI switching is A->B->C->D->E->A
>
> it doesn't mean the B going into C makes sense or D going into E makes
> sense, it's just how the UI is built. You give meaning to the states and
> what states transitions are valid (in your world). Like many things, org
> gives some structure to work with and we need to give the meaning.
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?
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? Org-Edna...?
--
David Masterson
next prev parent reply other threads:[~2023-01-17 18:13 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 [this message]
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=SJ0PR03MB5455A5601A51868125D397C8A2C69@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson@gmail.com \
--cc=danflscr@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).