emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ox] possible to modify org-export-document-properties OTG
Date: Sun, 22 Mar 2015 15:12:45 +0100	[thread overview]
Message-ID: <87mw352k9u.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87r3shvmqr.fsf@gmx.us> (rasmus@gmx.us's message of "Sun, 22 Mar 2015 02:34:20 +0100")

Rasmus <rasmus@gmx.us> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>>        (:subject "SUBJECT" nil nil parsed)
>> `parsed' behavior implies `space' anyway, since we're talking about
>> secondary strings.
> Is that always the case?  I guess..

There are only two ways to look at it: either it can only contain
objects, or it can contain paragraphs. The latter might make sense for,

In this case, we need 2 symbols for that, e.g., `parse-objects' and

>> `org-element-map' can find objects in captions, with an optional
>> argument.
> If turns out to be important, perhaps it would also be possible to map
> keyword objects with an non-default argument.

This is different. Captions are already in the parse tree. Keyword
objects are added mid-way. I'd rather keep keywords as is. If you want
to map over objects in, e.g., SUBJECT, you need to explicitly call
`org-element-map' on (plist-get info :subject).


      reply	other threads:[~2015-03-22 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17  0:58 [ox] possible to modify org-export-document-properties OTG Rasmus
2015-03-17  8:25 ` Nicolas Goaziou
2015-03-18 16:42   ` Rasmus
2015-03-21 23:10     ` Nicolas Goaziou
2015-03-22  0:06       ` Rasmus
2015-03-22  1:06         ` Nicolas Goaziou
2015-03-22  1:34           ` Rasmus
2015-03-22 14:12             ` Nicolas Goaziou [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:

  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=87mw352k9u.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \


* 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


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