emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Invalid read syntax (#) in org-element parse tree
Date: Tue, 12 Feb 2013 20:41:24 +0100	[thread overview]
Message-ID: <87zjz99v6j.fsf@gmail.com> (raw)
In-Reply-To: <87r4kmbfon.fsf@gmail.com> (Thorsten Jolitz's message of "Tue, 12 Feb 2013 00:20:56 +0100")

Thorsten Jolitz <tjolitz@gmail.com> writes:

>> I'm not sure about what you want to do with the parse tree. The usual
>> function to work with it is `org-element-map'. You may want to have
>> a look at its docstring, as it contains examples.
>
> I want to write an 'unusual' backend that does not need anything else
> from the exporting framework but the parse-tree as a list. 

Then you don't want the exporting framework at all, only org-element.el.

Anyway I'm confused. The parse-tree _is_ a list. To convince yourself,
evaluate the following in any Org buffer:

  (listp (org-element-parse-buffer))

> So all I need would be a workaround for this read-error issue, i.e.
> a tip how to get a version of the parse tree that can be used as list
> in a Lisp program.

Have you tried (setq print-circle t) ?

> I could not find any explanation for the '#1' and '#2' syntax I
> encountered, so I don't really know what its all about.

It is explained in the info link I gave you.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2013-02-12 19:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 18:29 Invalid read syntax (#) in org-element parse tree Thorsten Jolitz
2013-02-11 21:47 ` Nicolas Goaziou
2013-02-11 23:20   ` Thorsten Jolitz
2013-02-12 19:41     ` Nicolas Goaziou [this message]
2013-02-12 20:47       ` Thorsten Jolitz
2013-02-12 20:56         ` Thorsten Jolitz

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

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).