From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-koma-letter: how to use @@LaTeX:@@ specific commands in #+ directives
Date: Thu, 18 Jun 2015 00:03:54 +0200 [thread overview]
Message-ID: <87twu66lh1.fsf@selenimh.access.network> (raw)
In-Reply-To: <87bngexeyv.fsf@gmx.us> (rasmus@gmx.us's message of "Wed, 17 Jun 2015 22:22:16 +0200")
Hello,
Rasmus <rasmus@gmx.us> writes:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> Dear all,
>>
>> I have started using ox-koma-letter from the contrib directory. Very
>> nice. Thanks Nicolas, Alan, Viktor, and Rasmus!
>>
>> Everything works well so far except for one minor niggle: I would like
>> to introduce, sometimes, LaTeX specific inline directives in #+
>> lines. E.g. for LaTeX export, I would use @@latex:\\@@ to get a line
>> break in a title or author entry. I had expected the same to work with
>> ox-koma-letter given that it is a latex /derived/ backend and does work
>> in normal text, just not in #+ lines.
I cannot reproduce it. koma-letter back-ends explicitly allows latex
export snippets, e.g.,
#+title: @@latex:\something@@
produces the expected \something.
> It also doesn't work with ox-beamer:
>
> #+subtitle: subtitle @@latx:\LaTeX@@ @@beamer:BEAMER@@
>
> I guess it's a feature. Or a bug at a higher level than
> ox-koma-letter.
This is a feature.
If @@latex:...@@ is supported in beamer export, you have no way to
insert latex-only code in a document that you plan to export using both
beamer and latex back-ends.
However, this doesn't apply in koma-letter.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-06-17 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 17:32 ox-koma-letter: how to use @@LaTeX:@@ specific commands in #+ directives Eric S Fraga
2015-06-17 20:22 ` Rasmus
2015-06-17 22:03 ` Nicolas Goaziou [this message]
2015-06-17 22:55 ` Rasmus
2015-06-18 8:06 ` Eric S Fraga
2015-06-18 8:47 ` Rasmus
2015-06-18 9:09 ` Eric S Fraga
2015-06-18 21:01 ` Rasmus
2015-06-19 14:24 ` Eric S Fraga
2015-06-19 15:28 ` Eric S Fraga
2015-06-18 14:07 ` 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:
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=87twu66lh1.fsf@selenimh.access.network \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).