BUG: Filtering the agenda can cause actions on the wrong task

BUG: Filtering the agenda can cause actions on the wrong task

[Christopher Allan Webber]

Hello!

Say I have a couple of entries on my agenda:

  life:       Sched.25x:  TODO Places to notify change of address
  ccommons:   Sched.19x:  TODO Public domain mark                        :work::

My cursor is hovered over the "notify change of address" task.  I then
filter the agenda to the work tab with "/ <TAB> work <RET>".

Now my cursor is on the "Public domain mark", but if I do any action
it'll act on the (now invisible) change of address task.  If I press
enter, it'll jump to the change of adddress task, if I press t, it'll
change the TODO state, etc.

I've accidentally mis-closed a few tasks this way...

What I'm guessing needs to happen is somehow after the filtering takes
place that point needs to *actually* get moved, which I'm guessing it
doesn't currently?

I'm experiencing this error in git master.  Thanks!
 - Christopher Allan Webber

Re: BUG: Filtering the agenda can cause actions on the wrong task

[David Maus]

[-- Attachment #1.1: Type: text/plain, Size: 1516 bytes --]

Christopher Allan Webber wrote:
>Hello!

>Say I have a couple of entries on my agenda:

>  life:       Sched.25x:  TODO Places to notify change of address
>  ccommons:   Sched.19x:  TODO Public domain mark                        :work::

>My cursor is hovered over the "notify change of address" task.  I then
>filter the agenda to the work tab with "/ <TAB> work <RET>".

>Now my cursor is on the "Public domain mark", but if I do any action
>it'll act on the (now invisible) change of address task.  If I press
>enter, it'll jump to the change of adddress task, if I press t, it'll
>change the TODO state, etc.

>I've accidentally mis-closed a few tasks this way...

>What I'm guessing needs to happen is somehow after the filtering takes
>place that point needs to *actually* get moved, which I'm guessing it
>doesn't currently?

I can confirm this with

Org-mode version 7.01trans (release_7.01h.438.g006eb)

GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
 of 2010-08-14 on raven, modified by Debian

With this minimal file:

,----
| * TODO Headline 1							:tag:
|   SCHEDULED: <2010-09-20 Mo>
| * TODO Headline 2
|   SCHEDULED: <2010-09-20 Mo>
| * TODO Headline 3 							:tag:
|   SCHEDULED: <2010-09-20 Mo>
`----

 - M-x org-agenda RET a
 - move point to second headline ("Headline 2")
 - / <TAB> tag RET

Now point is at the end of "Headline 1" but <TAB> jumps to the hidden
"Headline 2".

Best,
  -- David

--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: BUG: Filtering the agenda can cause actions on the wrong task

[Carsten Dominik]

On Sep 17, 2010, at 4:36 PM, Christopher Allan Webber wrote:

> Hello!
>
> Say I have a couple of entries on my agenda:
>
>  life:       Sched.25x:  TODO Places to notify change of address
>  ccommons:   Sched.19x:  TODO Public domain  
> mark                        :work::
>
> My cursor is hovered over the "notify change of address" task.  I then
> filter the agenda to the work tab with "/ <TAB> work <RET>".
>
> Now my cursor is on the "Public domain mark", but if I do any action
> it'll act on the (now invisible) change of address task.  If I press
> enter, it'll jump to the change of adddress task, if I press t, it'll
> change the TODO state, etc.
>
> I've accidentally mis-closed a few tasks this way...
>
> What I'm guessing needs to happen is somehow after the filtering takes
> place that point needs to *actually* get moved, which I'm guessing it
> doesn't currently?

I think this is a correct analysis.  I just fixed this bug, please  
verify!

David, thanks for taking the time to confirm this bug.

- Carsten