emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mark Elston <m_elston@comcast.net>
To: emacs-orgmode@gnu.org
Subject: Re: Re: Bug: LaTeX export and LaTeX environment
Date: Wed, 19 May 2010 12:20:16 -0700	[thread overview]
Message-ID: <4BF439F0.3030307@comcast.net> (raw)
In-Reply-To: <zf.upnr5l8z6yo.fsf@zeitform.de>

Ulf, Carsten,


On 5/19/2010 12:27 AM, Ulf Stegemann wrote:
> Hi Carsten,
>
> Carsten Dominik<carsten.dominik@gmail.com>  wrote:
>
>> On May 19, 2010, at 8:34 AM, Ulf Stegemann wrote:
>>
>>>  ...
>>> the LaTeX exporter seems to cease to work when encountering a LaTeX
>>> environment.
>>
>> it has always been like this,
>>
>> check out this entire thread for work-arounds and other solutions
>>
>> http://thread.gmane.org/gmane.emacs.orgmode/12977
>
> I must have been blind, thanks for the pointer! It works like a charm
> with org-special-blocks.
>
> Ulf

I have not looked into the contrib directory lately (for quite a while,
actually) so was not aware of the org-special-blocks stuff.  This is
pretty cool and *almost* what I was about to ask for as well.

The only problem I have with it is I need (for specific environments) to
pass a parameter to the \begin{xxx} call on latex export.  I think what
is there is a more than adequate basis for what I am looking to do and I
will add my stuff to it and try it out.

My question is:  Is there a preferred way of doing this?  I can do a
local enhancement that hard-codes what I am trying to do but would
prefer to do this is a more open-ended (even elegant) way.  At the
end of the day it simply has to work.  But I would prefer doing it
"right." :)

Mark

  reply	other threads:[~2010-05-19 19:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19  6:34 Bug: LaTeX export and LaTeX environment Ulf Stegemann
2010-05-19  6:57 ` Carsten Dominik
2010-05-19  7:27   ` Ulf Stegemann
2010-05-19 19:20     ` Mark Elston [this message]
2010-06-01 13:42       ` Carsten Dominik
2010-06-01 13:57         ` Chris Gray
2010-06-01 14:46           ` Carsten Dominik
2010-06-01 15:02           ` Chris Gray
2010-06-01 21:20             ` Mark Elston
2010-06-02  8:28               ` Chris Gray

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=4BF439F0.3030307@comcast.net \
    --to=m_elston@comcast.net \
    --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).