From: Chris Gray <chrismgray@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: markup in environments in latex export
Date: Thu, 16 Apr 2009 15:09:26 +0200 [thread overview]
Message-ID: <8663h47njt.fsf@portan.ibr.cs.tu-bs.de> (raw)
In-Reply-To: AE5312AB-F9A4-4D0B-8F90-52A7CAE83DCC@gmail.com
Carsten Dominik wrote:
> Hi Chris,
> you can't have the cake and eat it.
> if you insert a LaTeX environment, the entire environment
> will be protected. After all, you rely on this quoting with your
> itemize environment!
Hi Carsten,
I don't really understand this. I can see it for things like the
verbatim environment, but that might be a special case.
> However, you can do this:
> #+begin_center
I should have chosen a different example I suppose. What I am really
using, rather than center, are the theorem, lemma, and proof
environments. I thought it would be safer for my example to use an
environment that is included by default in LaTeX. Unfortunately, center
is already a special case in org. But I tried #+begin_proof and that
did not work.
> This works by the protection being done first, and only
> then #+begin_center is turned into \begin{center}
Perhaps that could be generalized so that #+begin_foo means "do the
regular org parsing and then turn on \begin{foo}"? Other exporters
would be free to ignore these commands.
I really like doing my work in org mode, and I can certainly convert my
markup commands to regular LaTeX, but doing that really seems like a
second-best solution.
Cheers,
Chris
next prev parent reply other threads:[~2009-04-16 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 8:49 markup in environments in latex export Chris Gray
2009-04-16 12:21 ` Carsten Dominik
2009-04-16 13:09 ` Chris Gray [this message]
2009-04-16 20:47 ` Carsten Dominik
2009-04-19 19:55 ` Chris Gray
2009-04-20 6:04 ` Carsten Dominik
2009-05-02 7:27 ` Carsten Dominik
2009-05-04 7:52 ` Chris Gray
2009-05-04 14:28 ` Carsten Dominik
2009-05-06 14:01 ` 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=8663h47njt.fsf@portan.ibr.cs.tu-bs.de \
--to=chrismgray@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).