From: Kyle Meyer <firstname.lastname@example.org>
To: Ihor Radchenko <email@example.com>
Cc: firstname.lastname@example.org, "Dinnyés Dániel" <email@example.com>
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: Mon, 17 Aug 2020 22:16:18 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Ihor Radchenko writes:
>> 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.
Thanks. With 9.1.9 (5e4542d69), that indeed does look to be an issue.
* TODO a
* TODO b :drop:
* TODO c
List those in the agenda, exclude drop, and, with point on a's line, hit
M-e (move-end-of-line). Point is then at the end of the invisible b,
and calling org-agenda-todo acts on b rather than a.
However, as of v9.3.3, specifically a2b69c58f (org-agenda.el: Add
`org-agenda-end-of-line', 2020-02-02), move-end-of-line is remapped and
point ends up at the end of a, avoiding the issue.
Are you able to trigger this "act on invisible entry" behavior with
bound navigation commands in recent Org versions?
next prev parent reply other threads:[~2020-08-18 2:16 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
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 [this message]
2020-08-18 2:43 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).