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: Can `org-element-map' act on secondary-strings?
Date: Sat, 06 Jul 2013 19:14:54 +0200	[thread overview]
Message-ID: <871u7bfw4x.fsf@gmail.com> (raw)
In-Reply-To: <87li5jrbx3.fsf@gmail.com> (Thorsten Jolitz's message of "Sat, 06 Jul 2013 16:38:32 +0200")

Hello,

Thorsten Jolitz <tjolitz@gmail.com> writes:

> when parsing an Org file with org-element-parse-buffer, headline titles
> and section contents (e.g.) end up as secondary strings in the
> parse-tree that do have a ':parent' attribute.
>
> When I try to modify all :parent attributes inside a parse-tree with
> `org-element-map' (by mapping over all element and object types), the
> secondary strings in the parse-tree remain untouched.
>
> Is there a way to make `org-element-map' act on these secondary strings
> too? 

I'm not sure to understand your question.

"Secondary string" is not an object type, so you cannot explicitly
search for them in a parse tree.

Also, secondary strings do not have a :parent property (or any property
whatsoever: they are just lists).

Though, if you map over objects, e.g., bold text, `org-element-map' will
also look for them within secondary lists.


HTH,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-07-06 17:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-06 14:38 Can `org-element-map' act on secondary-strings? Thorsten Jolitz
2013-07-06 17:14 ` Nicolas Goaziou [this message]
2013-07-08  7:16   ` Thorsten Jolitz
2013-07-08  7:39     ` Nicolas Goaziou
2013-07-08 12:06       ` Thorsten Jolitz
2013-07-08 13:00         ` Nicolas Goaziou
2013-07-08 13:48           ` Thorsten Jolitz
2013-07-08 14:08             ` Jambunathan K
2013-07-08 16:54               ` 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=871u7bfw4x.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
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).