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: missing element in org-element.el
Date: Fri, 19 Apr 2013 18:31:28 +0200	[thread overview]
Message-ID: <87txn2o527.fsf@gmail.com> (raw)
In-Reply-To: <87sj2mcz39.fsf@gmail.com> (Thorsten Jolitz's message of "Fri, 19 Apr 2013 17:35:54 +0200")

Thorsten Jolitz <tjolitz@gmail.com> writes:

> What about 
>
> ,----------------
> | latex-or-entity
> | plain-link
> | text-markup
> `----------------
>
> in 
>
> ,---------------------------------------------------------------------------------
> | (defconst org-element-all-successors
> |   '(export-snippet footnote-reference inline-babel-call inline-src-block
> |                    latex-or-entity line-break link macro plain-link radio-target
> |                    statistics-cookie sub/superscript table-cell target
> |                    text-markup timestamp)
> |   "Complete list of successors.")
> `---------------------------------------------------------------------------------
>
> ? 
>
> They seem to be neither elements nor objects - are they a kind of
> 'abstract categories' for some object types?
>
> And I must admit that I'm not sure about the exact meaning of
> 'successors'. You describe elements and objects in detail in the
> comment-section of org-element.el, but don't mention 'successors'.

I do, in the "Objects" section. Successors are functions used to find
the next object of a given type. Some objects are so close that they can
share the same successor. Hence `text-markup' is a successor shared by
underline, code, verbatim, bold, italic and strike-through objects. See
`org-element-object-successor-alist' for more information.

Also, see comments above `org-element--parse-elements' to get
information about the algorithm used for object research.

> I hope I don't go on your nerves with my questions, but I'm trying to
> understand how you modeled an Org-file and its not all clear to me.

There are comments at the beginning of each section in the file: these
should give you some answers. Don't hesitate to ask if they don't
fulfill your needs.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-04-19 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 14:30 Thorsten Jolitz
2013-04-19 14:37 ` Nicolas Goaziou
2013-04-19 15:35   ` Thorsten Jolitz
2013-04-19 16:31     ` Nicolas Goaziou [this message]
2013-04-19 16:41       ` 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=87txn2o527.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tjolitz@gmail.com \
    --subject='Re: missing element in org-element.el' \
    /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 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).