From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: org agenda search goes to wrong target location Date: Thu, 23 Jul 2009 20:09:38 -0400 Message-ID: <87skgnndq5.fsf@gollum.intra.norang.ca> References: <20524da70907231701t34f92a5co65187fad7dc51af1@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MU8MC-0002jP-Cs for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 20:09:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MU8M7-0002fb-Ut for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 20:09:51 -0400 Received: from [199.232.76.173] (port=57206 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MU8M7-0002fT-Q3 for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 20:09:47 -0400 Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:50620) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MU8M7-0004ql-C7 for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 20:09:47 -0400 In-Reply-To: <20524da70907231701t34f92a5co65187fad7dc51af1@mail.gmail.com> (Samuel Wales's message of "Thu\, 23 Jul 2009 17\:01\:36 -0700") 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: Samuel Wales Cc: emacs-orgmode Samuel Wales writes: > Very often, when I do a keyword search in the agenda (m-x > agenda RET s), org-agenda-switch-to (RET) goes to the wrong > location in the target file. To sync it, the easiest way that I have > found so far is > to open all agenda buffers, kill all agenda buffers, open > all agenda buffers, and run the search again. > > Is there an easier way? Does it consistently go to the wrong place? I've seen issues where the RET in the agenda goes to the wrong location once but then doing it a second time it works fine. Unfortunately I don't have any insight about why this occurs or how to fix it. -Bernt