From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Beck Subject: Re: org-map-entries moves point Date: Wed, 05 Feb 2014 23:10:57 +0100 Message-ID: <52F2B6F1.6040102@miszellen.de> References: <52F295B1.6090806@miszellen.de> <87mwi5uvh2.fsf@alphaville.bos.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52965) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBBO7-0001Dv-J9 for emacs-orgmode@gnu.org; Wed, 05 Feb 2014 17:56:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WBBO2-0003yI-IU for emacs-orgmode@gnu.org; Wed, 05 Feb 2014 17:56:11 -0500 Received: from mo6-p00-ob.smtp.rzone.de ([2a01:238:20a:202:5300::11]:20877) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WBBO2-0003xq-4F for emacs-orgmode@gnu.org; Wed, 05 Feb 2014 17:56:06 -0500 In-Reply-To: <87mwi5uvh2.fsf@alphaville.bos.redhat.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nick Dokos , emacs-orgmode@gnu.org On 05.02.2014 21:59, Nick Dokos wrote: > John Kitchin reported this last week and Bastien reverted that commit: > > http://thread.gmane.org/gmane.emacs.orgmode/81587 Missed that. But this reverts commit 3ec38f5c064c3270f54876ba33c5ca1097b46853 [1] (in org-map-entries) I was talking about fe3379bda6ca23474639b114592958bf14431c88 [2] (which did the same to org-agenda-prepare-buffer) In fact, the revert *caused* my bug. Again, the recipe: The bug doesn't really move the point, rather it recenters the current line. To see it, move into the middle of a document, unfold a second level headline and in the middle of the window execute (org-map-entries (lambda () ;; do something or even nothing ) nil 'tree) This works correctly if either commit [1] is restored or [2] is reverted. > But it's not clear *why* that commit was done in the first place so if > you get some enlightenment from your experiments, please share. Will do. > > Nick > > > -- Florian Beck