emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Custom environment for LaTeX export
Date: Mon, 11 Aug 2014 11:24:30 +0200	[thread overview]
Message-ID: <20140811092430.GB2336@chitra.no-ip.org> (raw)
In-Reply-To: <877g2gvni9.fsf@free.fr>

On Sun, Aug 10, 2014 at 08:59:10AM +0200, Julien Cubizolles wrote:
> 
> 
> Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
> writes:
> 
> 
> > Throwing an idea here: make the `consequence' environment be a no-op in Beamer?
> 
> How would I do that, is there a variable excluding some environments ?

I'm guessing Seb's idea could be implemented by redefining the
consequence environment when in beamer, leave it alone otherwise.

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.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.

next prev parent reply	other threads:[~2014-08-11  9:24 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 [this message]
2014-08-14 15:03       ` Sebastien Vauban
2014-08-15  9:46         ` Suvayu Ali
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=20140811092430.GB2336@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

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