From: Ihor Radchenko <yantar92@gmail.com>
To: "Kyle Meyer" <kyle@kyleam.com>, "Dinnyés Dániel" <dinnyesd@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-agenda-todo applied to wrong line item [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)]
Date: Sun, 16 Aug 2020 19:37:48 +0800 [thread overview]
Message-ID: <87v9hihldf.fsf@localhost> (raw)
In-Reply-To: <87k0xzamdy.fsf@kyleam.com>
> Using Emacs 26.3 with a vanilla configuration and the Org repo checked
> out at 5e4542d69 (the commit reported in the subject line), I didn't see
> the behavior you describe. With point at the end of the agenda line for
> A, the state was changed for A.
I think that may happen when you have agenda filter active and an entry
hidden by filter is between the current and next line.
Best,
Ihor
Kyle Meyer <kyle@kyleam.com> writes:
> Dinnyés Dániel writes:
>
>> While in the Org Agenda, and navigating to the end of line for a given item
>> (assuming more than one todo items), and calling org-agenda-todo (with
>> keybindings t, or C-c C-t)... this result in the call being applied to the
>> next line item, instead of the one the cursor is on.
>>
>> This only happens when the cursor is at the end of the line.
>>
>> I would consider this to be a bug.
>
> I tried using the following content as the agenda file:
>
> * TODO A
> * TODO B
>
> Using Emacs 26.3 with a vanilla configuration and the Org repo checked
> out at 5e4542d69 (the commit reported in the subject line), I didn't see
> the behavior you describe. With point at the end of the agenda line for
> A, the state was changed for A.
>
> I also can't trigger the behavior with the master branch checked out.
next prev parent reply other threads:[~2020-08-16 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 16:07 Bug: org-agenda-todo applied to wrong line item [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/)] Dinnyés Dániel
2020-08-15 16:45 ` Kyle Meyer
2020-08-16 11:37 ` Ihor Radchenko [this message]
2020-08-16 15:01 ` Dinnyés Dániel
2020-08-16 15:34 ` Dinnyés Dániel
2020-08-18 2:45 ` Kyle Meyer
2020-10-18 5:16 ` Daniel Dinnyes
2020-08-18 2:16 ` Kyle Meyer
2020-08-18 2:43 ` 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=87v9hihldf.fsf@localhost \
--to=yantar92@gmail.com \
--cc=dinnyesd@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.com \
/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).