emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: the "right way" to build OMPL export and import
Date: Fri, 26 Apr 2013 23:49:59 +0200	[thread overview]
Message-ID: <87obd155dk.fsf@gmail.com> (raw)
In-Reply-To: <87y5c5ou7h.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 26 Apr 2013 14:30:58 -0700")

Hello,

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> I'm not sure the general export engine is going to be of much use,
> since XML is so completely flexible, but you'll definitely want to
> build it on top of the internal parser.

It would be a bad idea not to use the export framework, unless you want
to reinvent the wheel (e.g., re-implementing skipping of :noexport:
tags).

> Luckily, the parser turns an org subtree into a parse tree, and the
> function `xml-print' turns a parse tree into XML. They're not quite the
> same parse tree, but I guess you'll want to do something like this:
>
>
> #+BEGIN_SRC org
>   ,* My Great Playlist
>   ,** The Cold Cold Ground.mp3
>   :PROPERTIES:
>   :OPML_TYPE: song
>   :OPML_F:   Tom Waits - The Cold Cold Ground
>   :END:
>   ,** Don't Eat the Yellow Snow.mp3
>   :PROPERTIES:
>   :OPML_TYPE: song
>   :OPML_F:   Frank Zappa - Don't Eat the Yellow Snow
>   :END:
> #+END_SRC
>
>
> |
> |
> org-element--parse-elements

Please use `org-element-parse-buffer' instead. As the two consecutive
hyphens suggest, this is an internal function.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-04-26 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 20:25 the "right way" to build OMPL export and import Alexis Gallagher
2013-04-26 21:30 ` Eric Abrahamsen
2013-04-26 21:49   ` Nicolas Goaziou [this message]
2013-04-26 22:23     ` Eric Abrahamsen
2013-04-26 22:36       ` Nicolas Goaziou
2013-04-27  4:51         ` Eric Abrahamsen

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