From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: BUG: Filtering the agenda can cause actions on the wrong task Date: Mon, 20 Sep 2010 20:24:36 +0200 Message-ID: References: <87bp7w3098.fsf@dustycloud.org> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=43417 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oxl2f-0004dp-Tk for emacs-orgmode@gnu.org; Mon, 20 Sep 2010 14:24:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oxl2e-0000Df-Uj for emacs-orgmode@gnu.org; Mon, 20 Sep 2010 14:24:41 -0400 Received: from mail-ew0-f41.google.com ([209.85.215.41]:36105) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Oxl2e-0000DT-LR for emacs-orgmode@gnu.org; Mon, 20 Sep 2010 14:24:40 -0400 Received: by ewy28 with SMTP id 28so2158489ewy.0 for ; Mon, 20 Sep 2010 11:24:39 -0700 (PDT) In-Reply-To: <87bp7w3098.fsf@dustycloud.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Christopher Allan Webber Cc: emacs-orgmode@gnu.org 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 "/ work ". > > 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