From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: problem with org-refile remains in 5.20 Date: Fri, 8 Feb 2008 11:43:01 +0100 Message-ID: <92867819-9F85-4D17-BAE2-9D26500D014F@science.uva.nl> References: <87sl0528jt.fsf@web.de> <87k5lg4nms.fsf@web.de> Mime-Version: 1.0 (Apple Message framework v915) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JNQhL-000741-6R for emacs-orgmode@gnu.org; Fri, 08 Feb 2008 05:43:11 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JNQhJ-00072I-Lm for emacs-orgmode@gnu.org; Fri, 08 Feb 2008 05:43:09 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JNQhJ-00072E-Ey for emacs-orgmode@gnu.org; Fri, 08 Feb 2008 05:43:09 -0500 Received: from hu-out-0506.google.com ([72.14.214.226]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JNQhJ-0006Ud-2I for emacs-orgmode@gnu.org; Fri, 08 Feb 2008 05:43:09 -0500 Received: by hu-out-0506.google.com with SMTP id 23so5987012huc.1 for ; Fri, 08 Feb 2008 02:43:07 -0800 (PST) In-Reply-To: <87k5lg4nms.fsf@web.de> 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: Jost Burkardt Cc: emacs-org On Feb 7, 2008, at 7:39 PM, Jost Burkardt wrote: > > I think the reason, I get this behaviour is the following code in > org-refile: > ... > (goto-char (or (save-excursion > (if reversed > (outline-next-heading) > (outline-get-next-sibling))) > (point-max))) > ... > > before org-refile moves the point to the correct position, as I have > not > set `reversed', outline-get-next-sibling is called, as there is no > sibling to "*** Notes" the point is moved to "** B", but the call > returns nil, so finally (point-max) moves to the end of the file. Thanks, I can see it now - I am using reversed notes, so that is why I could not reproduce the problem. This is fixed in the git repository, will be in the next release. Thanks for being persistent. - Carsten