From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eddward DeVilla" Subject: Re: FR: headline iteration API Date: Wed, 11 Jun 2008 12:15:11 -0500 Message-ID: References: <20080530124619.GB9520@atlantic.linksys.moosehall> <9592BB6CDB1CEB48826BE86ACD71FA996ABF8D@kwik.ic.uva.nl> <20080611110623.GC19396@atlantic.linksys.moosehall> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K6Tul-0004KS-OY for emacs-orgmode@gnu.org; Wed, 11 Jun 2008 13:15:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K6Tuj-0004KG-AV for emacs-orgmode@gnu.org; Wed, 11 Jun 2008 13:15:14 -0400 Received: from [199.232.76.173] (port=57324 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6Tuj-0004KD-5I for emacs-orgmode@gnu.org; Wed, 11 Jun 2008 13:15:13 -0400 Received: from wf-out-1314.google.com ([209.85.200.175]:45620) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K6Tui-0008Q7-UM for emacs-orgmode@gnu.org; Wed, 11 Jun 2008 13:15:13 -0400 Received: by wf-out-1314.google.com with SMTP id 28so3271140wfc.24 for ; Wed, 11 Jun 2008 10:15:11 -0700 (PDT) In-Reply-To: <20080611110623.GC19396@atlantic.linksys.moosehall> Content-Disposition: inline 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: Adam Spiers , org-mode mailing list Are the functions behind C-c C-N, C-c C-p, C-c C-f, C-c C-b & C-c C-u available? Seems you could add a function for going to the first child. As long as that, C-c C-f & C-c C-b all return something to let you know there isn't a next, this should be pretty complete. I guess all you would need would be the following functions which would move to the correct place or return something to say there isn't a next/parent/child/sibling etc to signal the end of iteration. - doc traversal - first-item Go to the first item in the file. - current-item Go to the beginning of the item containing the cursor. - next-item Go to the item after the current one. - previous-item Go to item before the current one - tree traversal - parent-item Go to the parent item of the current item - first-child-item Go to the first item contained in the current item - next-sibling-item Go to the next item that has the same parent - previous-sibling-item Go to the previous item that has the same parent This ought to be enough to try to implement anything else on top of it. Did I miss something? Edd On Wed, Jun 11, 2008 at 6:06 AM, Adam Spiers wrote: > On Wed, Jun 11, 2008 at 08:57:39AM +0200, Dominik, C. wrote: >> Hi Adam and others, >> >> I do like the idea of an API to iterate of entries and outline trees. >> For now, I am following this discussion to see what ideas pop up. >> When I find the time, something will be implemented. > > Great. As you can see from my other post, another use case just > popped up. > > Am I right in thinking that you must already have a lot of the code > for this? Presumably agenda generation and export must both do > headline iteration in a similar manner? > > Full-blown reporting would be seriously cool. Think: pretty coloured > graphs showing how the contents of your TODO lists vary over the days, > weeks, months ... :-) Very useful for trending, planning, ensuring > that the various areas of your life are kept in balance according to > your "30,000-50,000 foot views", as David Allen calls them. > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode >