emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: getting file properties
Date: Sun, 05 May 2013 09:36:24 +0200	[thread overview]
Message-ID: <87r4hlg9on.fsf@gmail.com> (raw)
In-Reply-To: <87vc6ym4az.fsf@pierrot.dokosmarshall.org> (Nick Dokos's message of "Sun, 05 May 2013 00:36:04 -0400")

Hello,

Nick Dokos <ndokos@gmail.com> writes:

> Here's one way:
>
> (defun jk-org-kwds ()
>   (let* ((parse-tree (org-element-parse-buffer))
> 	 (keys (org-element-map parse-tree 'keyword (function identity))))
>     (mapcar (function  (lambda (x) (cons (org-element-property :key x)
> 					 (org-element-property :value x)))) keys)))
>
> This returns a list of (KEY. VALUE) pairs.
>
> I'm sure there are other (better, cheaper) ways, but I'm going through
> org-element.el, and having that hammer in hand, everything looks like
> a nail to me :-)

I suggest the slightly more efficient variation:

  (defun jk-org-kwds ()
    (org-element-map (org-element-parse-buffer 'element) 'keyword
      (lambda (keyword) (cons (org-element-property :key keyword)
                         (org-element-property :value keyword)))))

The optional argument `element' prevents `org-element-parse-buffer' from
diving too deep and `org-element-map' does the job of `mapcar'.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-05-05  7:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-04 21:42 getting file properties John Kitchin
2013-05-05  1:51 ` J. David Boyd
2013-05-05  4:36   ` Nick Dokos
2013-05-05  7:36     ` Nicolas Goaziou [this message]
2013-05-05  5:11 ` Eric Abrahamsen
  -- strict thread matches above, loose matches on Subject: below --
2013-05-05 16:34 John Kitchin

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=87r4hlg9on.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /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).