From: Nick Dokos <nicholas.dokos@hp.com>
To: Richard Lawrence <richard.lawrence@berkeley.edu>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: org-map-entries and org-map-continue-from
Date: Mon, 28 Feb 2011 14:02:39 -0500 [thread overview]
Message-ID: <26540.1298919759@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Richard Lawrence <richard.lawrence@berkeley.edu> of "Mon, 28 Feb 2011 10:40:24 PST." <87oc5watpj.fsf@berkeley.edu>
Richard Lawrence <richard.lawrence@berkeley.edu> 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 ((org-trust-scanner-tags t))
> (push (org-entry-get (point) "EXPORT_FILE_NAME") export-files)))
> nil 'tree)
> (message export-files))) ; errors, but lets me see the list of collected values
> #+END_SRC
>
As you point out below, everything works as it should: outline-next-heading
steps you through the headlines and eventually returns nil
correctly. 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.
But I'm not sure what the right way to deal with it is.
Nick
> And I call this function from a buffer that looks like:
>
> * Top
> <point is here when I call get-export-filenames>
> ** One
> :PROPERTIES:
> :EXPORT_FILE_NAME: one
> :END:
> ** Two
> :PROPERTIES:
> :EXPORT_FILE_NAME: two
> :END:
> ** Three
> :PROPERTIES:
> :EXPORT_FILE_NAME: three
> :END:
> ** Four
> :PROPERTIES:
> :EXPORT_FILE_NAME: four
> :END:
>
> Then the list that I get back (the value of export-files) looks like:
>
> ("four" "four" "three" "two" "one")
>
> Whereas I would like it to be just:
>
> ("four" "three" "two" "one")
>
> Can anyone see what I need to do to achieve that? [Apart from just using
> (cdr export-files), I mean -- I'd like to know the /right/ way.] I'm
> puzzled because outline-next-heading, if called interactively from the
> last child, does indeed put point at the end of that child or at the
> next (parent-level) heading, so it doesn't seem that the problem is that
> it somehow loops back when there is no next child-level entry.
>
> Many thanks if you catch something I've missed!
>
> Best,
> Richard
>
> [1] http://article.gmane.org/gmane.emacs.orgmode/37244/
>
next prev parent reply other threads:[~2011-02-28 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 18:40 org-map-entries and org-map-continue-from Richard Lawrence
2011-02-28 19:02 ` Nick Dokos [this message]
2011-02-28 19:14 ` Nick Dokos
2011-03-01 4:01 ` Richard Lawrence
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26540.1298919759@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=richard.lawrence@berkeley.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).