From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: How to deal with 'contents' in (derived) exporter backend
Date: Wed, 06 Nov 2013 15:36:32 +0100 [thread overview]
Message-ID: <87vc05sikv.fsf@gmail.com> (raw)
In-Reply-To: 878ux2d2g5.fsf@gmail.com
Hello,
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Thorsten Jolitz <tjolitz@gmail.com> writes:
>
>> But when I use something like this in the headline transcode function
>>
>> #+begin_src emacs-lisp
>> (format "(headline %S %s) "
>> [... return headline string ...]
>> contents)
>> #+end_src
>>
>> I get the parse-tree structure as output instead of elements/object
>> in their original Org text syntax as expected:
>>
>> #+begin_src emacs-lisp
>> (org-data nil "(headline (title-string \"A1\" alt-title-string \"A1\"
>> category \"tmp5\" level 1 priority nil tags nil todo-keyword nil
>> quotedp nil archivedp nil commentedp nil footnote-secion-p nil)
>> (section (#(\"Text *A1* \" 0 5 (:parent (paragraph (:begin 6 :end 16
>> :contents-begin 6 :contents-end 16 :post-blank 0 :post-affiliated 6
>> :parent (section (:begin 6 :end 16 :contents-begin 6 :contents-end 16
>> :post-blank 0 :parent (headline (:raw-value \"A1\" :begin 1 :end 32
>> :pre-blank 0 :contents-begin 6 :contents-end 32 :level 1 :priority nil
>> :tags [...]
>> #+end_src
>
> You don't get the parse-tree structure, you get Org syntax within
> a propertized string. Try (org-no-properties contents) instead.
That does the trick, thank you very much, I was kind of stuck without
being aware of this function.
--
cheers,
Thorsten
prev parent reply other threads:[~2013-11-06 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 12:30 How to deal with 'contents' in (derived) exporter backend Thorsten Jolitz
2013-11-05 20:21 ` Nicolas Goaziou
2013-11-06 14:36 ` Thorsten Jolitz [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vc05sikv.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.