emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [ox] possible to modify org-export-document-properties OTG
Date: Wed, 18 Mar 2015 17:42:01 +0100	[thread overview]
Message-ID: <87iodytfza.fsf@gmx.us> (raw)
In-Reply-To: <87k2yg115l.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 17 Mar 2015 09:25:10 +0100")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Document properties are keywords where `org-element-context' is allowed
> to return an object. It doesn't make sense to add random keywords
> specific to some export back-ends to the list.

I think something like SUBJECT in ox-koma-letter makes sense.  But what
I'm really after is an "easy" way to control org-export-data from the
backend definition.

>> Or should org-element-parse-secondary-string be used with appropriate
>> limitations?
> For now, I suggest to use `org-element-parse-secondary-string'.

Why I don't like this is that it feels quite low-level (purely emotional)

    (org-export-data (oe-parse-2nd-string ⋯) ⋯)

> At some point, I thought about adding a `parsed' behaviour to
> `org-export-options-alist' as a shortcut.

Presumably you'd want to be able to toggle it for elements of

> Sadly, I cannot remember why I didn't implement the idea eventually. It
> may be related to `org-element-map', which couldn't map over data in
> such keywords, or the fact that it would be confusing wrt
> `org-element-context'. E.g., if we consider the two keywords
>   #+TITLE: *boXld*
> in the former, `org-element-context' at "X" returns a `bold' object, in
> the latter, a `keyword' element. Note that I'm not arguing it should
> return a `bold' object in both cases, it really shouldn't, but it can be
> confusing and potentially trigger false bug reports.

I don't understand why an export setting would affect an element
interpretation such as org-element-map.  Probably I have something
different in mind than you.


However beautiful the theory, you should occasionally look at the evidence

  reply	other threads:[~2015-03-18 16:42 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 [this message]
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

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


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