From: Nick Dokos <nicholas.dokos@hp.com>
To: "Levy, Roger" <rlevy@ucsd.edu>
Cc: nicholas.dokos@hp.com, Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Defining new structural markup element
Date: Wed, 14 Dec 2011 12:47:30 -0500 [thread overview]
Message-ID: <6467.1323884850@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from "Levy, Roger" <rlevy@ucsd.edu> of "Wed, 14 Dec 2011 17:33:03 GMT." <3496BDF0-8057-4079-95BF-9C6B25251602@ucsd.edu>
Levy, Roger <rlevy@ucsd.edu> wrote:
> Hi,
>
> I'm a relative org newbie and I expect that this question is answered somew=
> here in the manual, but I've searched and I can't find the answer.
>
> I would like to define a new structural markup element for an org file and =
> specify its translation into latex. e.g., I'd like to be able to put in my=
> document
>
> #+begin_foo
> bar
> #+end_foo
>
> and have this translated into LaTeX as something like=20
>
> \em
> bar
> \em
>
> but I'd like to be able to flexibly specify the LaTeX commands inserted at =
> the beginning and end of the "foo" block. Is there an easy way to do this?
>
Not sure I understand completely what you are trying to do, but you can
do something like this:
--8<---------------cut here---------------start------------->8---
* foo
#+LATEX: \begin{foo}
bar
#+LATEX: \end{foo}
--8<---------------cut here---------------end--------------->8---
to insert arbitrary LaTeX markup at the indicated places when exporting
to latex. Other exporters will just omit the markup.
Nick
next prev parent reply other threads:[~2011-12-14 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 17:33 Defining new structural markup element Levy, Roger
2011-12-14 17:47 ` Nick Dokos [this message]
2011-12-14 18:08 ` Viktor Rosenfeld
2011-12-14 19:06 ` Levy, Roger
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=6467.1323884850@alphaville.americas.hpqcorp.net \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=rlevy@ucsd.edu \
/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).