From: Philipp Kroos <philipp.kroos@t-online.de>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: subtree-export limitations
Date: Sat, 17 Nov 2012 16:12:05 +0100 [thread overview]
Message-ID: <877gpkb6wq.fsf@t-online.de> (raw)
In-Reply-To: <87txsonyka.fsf@gmail.com> (Nicolas Goaziou's message of "Sat, 17 Nov 2012 14:33:57 +0100")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> It might support "Property+" syntax, but it looks like this is
>> Babel-specific (no sign of such syntax in org.el, where property API is
>> defined). I will look into it (unless you want to do it).
>
> Well, scratch that: it already support :property+: syntax. I.e. try to
> export subtree with:
>
> * Test export
> :PROPERTIES:
> :export_latex_header: header1
> :export_latex_header+: header2
> :END:
>
> Test
Amazing! I didn't even know about the property+-syntax...
Now that's not as good as it *could* get since the headerlines are
separated by space rather than newline, but it's another very useful
option for a workaround at least.
After all, I think that a complete solution to this problem would break
the consistency of properties, like you said, or would have to introduce
yet another kind of syntax, what is clearly no option.
That said, I'm fine with the situation, but I'ld suggest a note in the
documentation that makes this limitation to subtree-exports clear (and
possibly points out the workarounds). What do you think?
Philipp
next prev parent reply other threads:[~2012-11-17 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 15:45 subtree-export limitations Philipp Kroos
2012-11-16 15:56 ` Alan Schmitt
2012-11-16 16:36 ` Suvayu Ali
2012-11-17 12:25 ` Philipp Kroos
2012-11-17 12:48 ` Nicolas Goaziou
2012-11-17 13:33 ` Nicolas Goaziou
2012-11-17 15:12 ` Philipp Kroos [this message]
2012-11-17 16:00 ` Nicolas Goaziou
2012-11-18 11:23 ` Philipp Kroos
2012-11-19 13:55 ` Alan Schmitt
2012-12-22 18:58 ` Bastien
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=877gpkb6wq.fsf@t-online.de \
--to=philipp.kroos@t-online.de \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).