emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: how can I create a new literal block for latex export?
Date: Tue, 23 Jun 2015 16:15:08 +0200	[thread overview]
Message-ID: <m2h9pytssz.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <87mvzq22iy.fsf@gmx.us> (rasmus@gmx.us's message of "Tue, 23 Jun 2015 11:32:37 +0200")

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

Hi Rasmus,

On 2015-06-23 11:32, Rasmus <rasmus@gmx.us> writes:

> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> Is there a way to tell org to leave the contents of myres blocks as-is?
>> Can I declare myres as a literal block?
>
> I think your issue here is similar to Jacob's a couple of weeks back.  I
> don't remember the outcome anymore, but check
>
>       http://thread.gmane.org/gmane.emacs.orgmode/97798

Thanks a lot for the link, I ended up using the solution from Charles
Berry:

have these header arguments

  :PROPERTIES:
  :header-args:js: :wrap latex :results output :exports both :post postenv("myres")
  :END:

and use this postenv wrapper

#+NAME: postenv
#+BEGIN_SRC emacs-lisp :var env="myres" :exports none
(format "$\\Rightarrow$ \\begin{%s}\n%s\\end{%s}" env *this* env)
#+END_SRC

The resulting latex is exactly what I want.

Thanks again,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Weekly CO₂ average (2015-05-30, Mauna Loa Observatory): 403.41 ppm

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

      parent reply	other threads:[~2015-06-23 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  8:47 how can I create a new literal block for latex export? Alan Schmitt
2015-06-23  9:32 ` Rasmus
2015-06-23 13:03   ` Nicolas Goaziou
2015-06-23 20:20     ` Alan Schmitt
2015-06-23 14:15   ` Alan Schmitt [this message]

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=m2h9pytssz.fsf@charm-ecran.irisa.fr \
    --to=alan.schmitt@polytechnique.org \
    --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).