From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: Re: Refiling goes to the wrong place Date: Fri, 28 Aug 2009 08:09:38 -0400 Message-ID: <87ocq0ywal.fsf@gollum.intra.norang.ca> References: <87d46hfcgb.fsf@gollum.intra.norang.ca> <87ljl5npts.fsf@in-ulm.de> <871vmxf6nu.fsf@gollum.intra.norang.ca> <05CE139F-15B3-443F-9659-B2CC824D6CD9@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 1Mh0H6-0007m5-Ay for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 08:09:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mh0H2-0007gL-H3 for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 08:09:47 -0400 Received: from [199.232.76.173] (port=55352 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mh0H2-0007g9-9s for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 08:09:44 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:49429) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mh0H1-00055o-Sm for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 08:09:44 -0400 In-Reply-To: <05CE139F-15B3-443F-9659-B2CC824D6CD9@gmail.com> (Carsten Dominik's message of "Fri\, 28 Aug 2009 08\:55\:26 +0200") 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: Carsten Dominik Cc: emacs-orgmode@gnu.org Carsten Dominik writes: > On Aug 27, 2009, at 8:33 PM, Bernt Hansen wrote: > > [long description omitted] > >> >> I'll be _really_ happy when Carsten squashes this bug :) > > Well, in that case I wish you a happy day. Lets hope that his was > the same bug that others have seen. > > Thank you *very* much for your persistence and the unsurpassed clarity > of your reports - it took a mere 5 minutes to find the problem. > > For those who are interested: The cause was the outline function > outline-get-next-sibling which does only find visible siblings. > By creating an inconsistent outline state using the org-clock-goto > function, Bernt created a visible sibling among invisible ones. > This was at least part of the problem. I hope it is fixed now. > At least, Bernt's example works now correctly. :) * Bernt does the happy dance \o/ Hopefully this is related to the agenda navigation (RET/TAB on an agenda item) goes to the wrong place issue we've seen in the past. I got lucky yesterday and stumbled across a case that triggered this bug more than once in my org files. I think we've been chasing this beast for over a year. Thanks again!!! -Bernt