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 02:06:56 +0100	[thread overview]
Message-ID: <87384x4z7z.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87vbhtvqtz.fsf@gmx.us> (rasmus@gmx.us's message of "Sun, 22 Mar 2015 01:06:00 +0100")

Rasmus <rasmus@gmx.us> writes:

> I /think/ that is what I would like.  But I don't understand the what you
> mean concretely: would you have something like:
>      (:subject "SUBJECT" nil nil space parsed)

       (:subject "SUBJECT" nil nil parsed)

`parsed' behavior implies `space' anyway, since we're talking about
secondary strings.


  (plist-get info :subject)

would return the same as the following, currently,

   (plist-get info :subject) (org-element-restriction 'keyword))

> I agree this is a difficult problem.  Personally, I think it is fine to
> consider a keyword as a keyword and nothing more, and not consider content
> within a keyword.  However, as I recall, John had a post a while back
> about mapping over bold in CAPTIONS or something like that.

`org-element-map' can find objects in captions, with an optional

> I think it may be a mess to interpret content of a keyword at
> org-element-map level.  Consider if #+SUBJECT is interpreted with in
> ox-koma-letter but not in an imaginary ox-new-letter.  Would it not be
> confusing?

I think so.


  reply	other threads:[~2015-03-22  1:05 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 [this message]
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=87384x4z7z.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).