From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Outline cycling does not preserve point's position Date: Wed, 11 Sep 2013 17:47:11 +0200 Message-ID: <87ppsf743k.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> <87d2oi57fg.fsf@gmail.com> <87ob80ko2a.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55099) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VJmdT-0004wz-RD for emacs-orgmode@gnu.org; Wed, 11 Sep 2013 11:47:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VJmdL-00035j-Pw for emacs-orgmode@gnu.org; Wed, 11 Sep 2013 11:47:19 -0400 Received: from plane.gmane.org ([80.91.229.3]:44967) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VJmdL-00035Q-JI for emacs-orgmode@gnu.org; Wed, 11 Sep 2013 11:47:11 -0400 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VJmdG-0006lR-V2 for emacs-orgmode@gnu.org; Wed, 11 Sep 2013 17:47:06 +0200 In-Reply-To: <87ob80ko2a.fsf@gmail.com> (Jambunathan K.'s message of "Wed, 11 Sep 2013 09:27:33 +0530") 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: Jambunathan K Cc: Bastien , public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org, Sebastien Vauban , Carsten Dominik Jambunathan K writes: > Hmmm... Object traversal. > > Now there should be a way to move between objects: Move to the next > object of the same type the cursor is on. This is interesting but not really possible at the moment. Currently Elements implement "successors" functions, which are basically a `re-search-forward' on some hard coded regexp and a predicate to check if we're really where we think we are. So moving to the next object is easy, but moving to the previous one would be awkward. In order to allow this, we should first change the innards of Elements and split "successors" in two parts: 1. an association list between object types and regexp 2. a predicate Then we would be able to move either way. If there's some real interest in it, I can have a look, but not right now. Regards, -- Nicolas Goaziou