From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Custom environment for LaTeX export
Date: Fri, 15 Aug 2014 11:46:09 +0200 [thread overview]
Message-ID: <20140815094609.GA2329@chitra.no-ip.org> (raw)
In-Reply-To: <86vbpv6rkx.fsf@somewhere.org>
Hi Seb,
On Thu, Aug 14, 2014 at 05:03:58PM +0200, Sebastien Vauban wrote:
>
> > However, I would like to suggest something a bit different. Why not
> > instead of #+BEGIN_consequence, you use a macro. Something like this:
> >
> > #+MACRO: cbeg @@latex:\begin{consequence}@@
> > #+MACRO: cend @@latex:\end{consequence}@@
> >
> > Then you can do:
> >
> > {{{cbeg}}}
> > stuff
> > {{{cend}}}
> >
> > and only LaTeX export will have the environment.
>
> That could be a good idea, but I'm pretty sure (99.999%) that LaTeX
> export snippets are read in Beamer -- though the opposite is false, it's
> useless for the problem at hand.
If I understood you correctly, you think LaTeX snippets will still be
exported when exporting to beamer, but not the other way around? If so,
I don't think that is correct. I'll do a quick test just to be
sure :-p.
Okay you are right! The above example when exported to either LaTeX or
beamer looks like this:
\begin{consequence}
stuff
\end{consequence}
This is a bit odd to me; is this a consequence of the fact that
ox-beamer derives from ox-latex? Is it a feature or a bug?
Anyway, given the above your suggestion seems to be the correct solution
for now.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2014-08-15 9:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 21:34 Custom environment for LaTeX export Julien Cubizolles
2014-07-28 14:52 ` Sebastien Vauban
2014-08-10 6:59 ` Julien Cubizolles
2014-08-11 9:24 ` Suvayu Ali
2014-08-14 15:03 ` Sebastien Vauban
2014-08-15 9:46 ` Suvayu Ali [this message]
2014-08-15 10:05 ` Nicolas Goaziou
2014-08-15 10:51 ` Suvayu Ali
[not found] ` <877g2gvni9.fsf-GANU6spQydw@public.gmane.org>
2014-08-14 9:15 ` Sebastien Vauban
2014-08-15 19:45 ` Marcin Borkowski
2014-08-25 16:32 ` Julien Cubizolles
2014-08-25 16:43 ` Marcin Borkowski
2014-08-25 17:38 ` Julien Cubizolles
2014-08-25 20:11 ` Marcin Borkowski
2014-08-25 16:53 ` Julien Cubizolles
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=20140815094609.GA2329@chitra.no-ip.org \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).