Re: [O] org-map-entries and org-map-continue-from

2011-02-28 Thread Richard Lawrence
Nick Dokos writes: > The problem is that org-entry-get does not just look forward: it looks > *around* and finds the property when point is both at the beginning > and at the end of the headline "Four", so you get "four" twice. Ah, so that's the culprit. Thanks! > Maybe this? > > #+BEGIN_SRC e

Re: [O] org-map-entries and org-map-continue-from

2011-02-28 Thread Nick Dokos
Nick Dokos wrote: > Richard Lawrence wrote: > > > > For a simple example, suppose I write: > > #+BEGIN_SRC emacs-lisp > > (defun get-export-filenames () > > (interactive) > > (setq export-files '()) > > (progn > > (org-map-entries > > (lambda () > >(setq org-map-continue

Re: [O] org-map-entries and org-map-continue-from

2011-02-28 Thread Nick Dokos
Richard Lawrence wrote: > For a simple example, suppose I write: > #+BEGIN_SRC emacs-lisp > (defun get-export-filenames () > (interactive) > (setq export-files '()) > (progn > (org-map-entries > (lambda () >(setq org-map-continue-from (outline-next-heading)) >(let

[O] org-map-entries and org-map-continue-from

2011-02-28 Thread Richard Lawrence
Hi all, Bastien had advised me [1] to use (setq org-map-continue-from (outline-next-heading)) in a function called by org-map-entries in order to map that function across just the /children/ of the current entry (i.e., to exclude the current `parent' entry itself). This works great, but I have