From: Kyle Meyer <kyle@kyleam.com>
To: Mario Frasca <mario@anche.no>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] select TODO items and unexpected behaviour
Date: Sun, 28 Jun 2020 16:04:19 -0400 [thread overview]
Message-ID: <87a70narek.fsf@kyleam.com> (raw)
In-Reply-To: <32b85f8a-3f26-15d8-8d93-cbdd222ab3db@anche.no>
[ Please don't drop the list in your replies. ]
Mario Frasca writes:
> if we were using self-evaluating symbols, the issue would vanish, and
> the code might result easier to read.
The "loop over headline" code in org-todo needs to be able to handle
every argument that org-todo accepts, including prefix arguments. A
wholesale rewrite of all of its arguments isn't an option.
> On 28/06/2020 01:32, Kyle Meyer wrote:
>> Should be fixed with
>> 8a2eb7d1b.
>
> I have an extra doubt on this feature. in fact, the completely
> independent rotation of status is not what I would expect. what I would
> expect is more like having several 3-way switches next to each other,
> and I pull them all together to a common position, stepwise … like,
> imagine the status is 1-2-0…
>
> times I activate the tool ->
>
> 0 1 2 3 …
> -----------
> 0 1 2 0
> 1 1 2 0
> 2 2 2 0
> 1 1 2 0
> 0 1 2 0
> 2 2 2 0
>
> now what happens is:
>
> 0 1 2 3 …
> -------------
> 0 1 2 0
> 1 2 0 1
> 2 0 1 2
> 1 2 0 1
> 0 1 2 0
> 2 0 1 2
This is orthogonal to the fix in 8a2eb7d1b. I do not have an opinion,
at least at the moment. Perhaps others that are interested will weigh
in.
next prev parent reply other threads:[~2020-06-28 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 21:16 [bug] select TODO items and unexpected behaviour Mario Frasca
2020-06-27 21:43 ` Mario Frasca
2020-06-27 21:54 ` Mario Frasca
2020-06-28 6:32 ` Kyle Meyer
2020-06-28 14:53 ` Mario Frasca
2020-06-28 18:50 ` Mario Frasca
2020-06-28 20:06 ` Kyle Meyer
[not found] ` <32b85f8a-3f26-15d8-8d93-cbdd222ab3db@anche.no>
2020-06-28 20:04 ` Kyle Meyer [this message]
2020-06-27 22:46 ` Russell Adams
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=87a70narek.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=mario@anche.no \
/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).