emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: A question on org-element-headline-interperter
Date: Fri, 03 Oct 2014 13:38:05 +0200	[thread overview]
Message-ID: <87lhoxxu1u.fsf@wmi.amu.edu.pl> (raw)
In-Reply-To: <871tqpaav3.fsf@gmail.com>


On 2014-10-03, at 09:08, Thorsten Jolitz wrote:

> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>
>> What is my misconception here?
>
> as I learned myself from Nicolas recently, these are internal functions,
> the API function for interpreting is 
>
> ,----[ C-h f org-element-interpret-data RET ]
> | org-element-interpret-data is an autoloaded compiled Lisp function in
> | `org-element.el'.
> | 
> | (org-element-interpret-data DATA &optional PSEUDO-OBJECTS)
> | 
> | Interpret DATA as Org syntax.
> | 
> | DATA is a parse tree, an element, an object or a secondary string
> | to interpret.
> | 
> | Optional argument PSEUDO-OBJECTS is a list of symbols defining
> | new types that should be treated as objects.  An unknown type not
> | belonging to this list is seen as a pseudo-element instead.  Both
> | pseudo-objects and pseudo-elements are transparent entities, i.e.
> | only their contents are interpreted.
> | 
> | Return Org syntax as a string.
> `----

Thanks a lot, that fixes my problem!  Now I'll move on to the next
one;-).  (I don't have it yet, but I'm sure I'll invent something.)

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

      reply	other threads:[~2014-10-03 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 23:16 A question on org-element-headline-interperter Marcin Borkowski
2014-10-03  7:08 ` Thorsten Jolitz
2014-10-03 11:38   ` Marcin Borkowski [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

  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=87lhoxxu1u.fsf@wmi.amu.edu.pl \
    --to=mbork@wmi.amu.edu.pl \
    --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 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).