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/)]

2020-10-17 Thread Daniel Dinnyes
I am currently on the master branch, and it seems to have been fixed indeed! On Tue, 18 Aug 2020 at 03:45, Kyle Meyer wrote: > Dinnyés Dániel writes: > > > I have tried reproducing it with a minimal example, and this seems to > work > > for me: > > > > * FOO > > ** TODO baz1 > > SCHEDULED:

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/)]

2020-08-17 Thread Kyle Meyer
Dinnyés Dániel writes: > I have tried reproducing it with a minimal example, and this seems to work > for me: > > * FOO > ** TODO baz1 > SCHEDULED: <2020-08-16 Sun> > > some text > > * BAR > ** TODO baz2 > SCHEDULED: <2020-08-16 Sun> > *** DONE baz3 > SCHEDULED: <2020-08-16 Sun> > *** TODO baz4 >

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/)]

2020-08-17 Thread Ihor Radchenko
> Are you able to trigger this "act on invisible entry" behavior with > bound navigation commands in recent Org versions? The org version of the move-end-of-line works fine on master. Though Org remapping does not affect my key binding setup (I use alternative version of move-end-of-line) and I

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/)]

2020-08-17 Thread Kyle Meyer
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

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/)]

2020-08-16 Thread Dinnyés Dániel
Made some corrections in the text below (marked with red). Also, removed the unnecessary "some text" from the body of baz1 item, as the issue can reproduce without it. On Sun, 16 Aug 2020 at 16:01, Dinnyés Dániel wrote: > I have tried reproducing it with a minimal example, and this works for

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/)]

2020-08-16 Thread Dinnyés Dániel
I have tried reproducing it with a minimal example, and this seems to work for me: * FOO ** TODO baz1 SCHEDULED: <2020-08-16 Sun> some text * BAR ** TODO baz2 SCHEDULED: <2020-08-16 Sun> *** DONE baz3 SCHEDULED: <2020-08-16 Sun> *** TODO baz4 SCHEDULED: <2020-08-16 Sun> When in the agenda, on

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/)]

2020-08-16 Thread Ihor Radchenko
> 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

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/)]

2020-08-15 Thread Kyle Meyer
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

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/)]

2020-08-15 Thread Dinnyés Dániel
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