From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Outline cycling does not preserve point's position Date: Mon, 09 Sep 2013 17:27:23 +0200 Message-ID: <87hadu582s.fsf@gmail.com> References: <868uz8sufg.fsf@somewhere.org> <86vc2cqvnb.fsf@somewhere.org> <86y57676t1.fsf@somewhere.org> <89E7FDB6-0F5A-4362-959C-C4B9844A235C@gmail.com> <86txhu7696.fsf@somewhere.org> <0A62C6DE-B3AD-458A-9AB4-92B61A6D3D63@gmail.com> <86ppsi75st.fsf@somewhere.org> <87eh8yo0el.fsf@bzg.ath.cx> <87li365ixg.fsf@gmail.com> <87wqmqjjut.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34713) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VJ3NL-0007i2-KY for emacs-orgmode@gnu.org; Mon, 09 Sep 2013 11:27:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VJ3NF-0005IH-1z for emacs-orgmode@gnu.org; Mon, 09 Sep 2013 11:27:39 -0400 Received: from plane.gmane.org ([80.91.229.3]:50587) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VJ3NE-0005GR-RC for emacs-orgmode@gnu.org; Mon, 09 Sep 2013 11:27:32 -0400 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VJ3ND-0001do-Gh for emacs-orgmode@gnu.org; Mon, 09 Sep 2013 17:27:31 +0200 In-Reply-To: <87wqmqjjut.fsf@bzg.ath.cx> (Bastien's message of "Mon, 09 Sep 2013 13:49:14 +0200") 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: Bastien Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org, Sebastien Vauban , Carsten Dominik Hello, Bastien writes: > But you got the idea: use `org-forward-element' when moving > within structural elements of various kinds make sense and use > `forward-paragraph' otherwise. No, I still don't get the idea, really. > It is predictable, but sometimes counter-intuitive: for example, when > on the first headline, C-up will throw an error instead of moving to > the top of the buffer. Sure, but otherwise it would conflict with your point below. > Also, it is predictable but not reversible: hitting C-down three times > then C-up three times will not always go back to the point where the > user was at the beginning. You need to return an error when there is no element at the same level. IIRC, it was initially the case. But then a user complained that, in the following example, X being the point: :PROPERTIES: X:PROP1: value :END: `org-forward-element' would return an error "Cannot move further down", which was difficult to understand. predictable, intuitive, reversible, pick two. Regards, -- Nicolas Goaziou