From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Question on org-beamer markup
Date: Wed, 12 Jan 2011 21:24:36 +0100 [thread overview]
Message-ID: <807he9hnuj.fsf@missioncriticalit.com> (raw)
In-Reply-To: 4D2DE792.8070502@ccbr.umn.edu
Hi Erik,
Erik Iverson wrote:
> According to http://orgmode.org/worg/org-tutorials/org-beamer/tutorial.html
>
> the following markup should work when exporting to PDF from an org-beamer
> document.
>
> - the first, very @important@, point!
> - the previous point shows the use of the special markup which
> translates to the Beamer specific /alert/ command for highlighting
> text.
>
> However, upon export the resulting .tex file does not actually contain this
> translation from @important@ to the alert command, but rather sill has
> @important@ in the output.
>
> Am I missing some part of the setup process?
You must update *manually* the var =org-export-latex-emphasis-alist=:
#+begin_src emacs-lisp
;; alist of LaTeX expressions to convert emphasis fontifiers
(setq org-export-latex-emphasis-alist
'(("*" "\\textbf{%s}" nil)
("/" "\\emph{%s}" nil)
("_" "\\underline{%s}" nil)
("+" "\\st{%s}" nil)
("=" "\\url{%s}" nil)
;; `url' breaks lines in long strings (was `verb')
("~" "\\verb~%s~" t)
("@" "\\alert{%s}" nil)))
#+end_src
This is an annoyance, yes... However, I don't have (yet?) a clever idea about
how to do this in a portable way, ie it should not cause problem when used in
non-beamer documents...
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-01-12 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 17:40 Question on org-beamer markup Erik Iverson
2011-01-12 20:24 ` Sébastien Vauban [this message]
2011-01-13 5:07 ` Rafael Villarroel
2011-01-13 16:41 ` Eric S Fraga
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=807he9hnuj.fsf@missioncriticalit.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).