From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Refiling goes to the wrong place Date: Fri, 28 Aug 2009 08:55:26 +0200 Message-ID: <05CE139F-15B3-443F-9659-B2CC824D6CD9@gmail.com> References: <87d46hfcgb.fsf@gollum.intra.norang.ca> <87ljl5npts.fsf@in-ulm.de> <871vmxf6nu.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgwCA-0003AX-HQ for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 03:48:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgwC5-00034v-No for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 03:48:25 -0400 Received: from [199.232.76.173] (port=38867 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgwC5-00034f-HM for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 03:48:21 -0400 Received: from mail-ew0-f211.google.com ([209.85.219.211]:56169) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgwC5-00087H-4O for emacs-orgmode@gnu.org; Fri, 28 Aug 2009 03:48:21 -0400 Received: by ewy7 with SMTP id 7so1859991ewy.31 for ; Fri, 28 Aug 2009 00:48:20 -0700 (PDT) In-Reply-To: <871vmxf6nu.fsf@gollum.intra.norang.ca> 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: Bernt Hansen Cc: emacs-orgmode@gnu.org 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. - Carsten