From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [org-beamer] \alert
Date: Tue, 26 Jan 2010 16:22:27 +0000 [thread overview]
Message-ID: <87k4v4omyk.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <877hr4zz0s.fsf@mundaneum.com>
At Tue, 26 Jan 2010 16:06:27 +0100,
Sébastien Vauban wrote:
> Eric S Fraga wrote:
> > At 24 Jan 2010 20:10:03 +0100,
> > Sven Bretfeld wrote:
> >>
> >> Is there any Symbol in org-beamer for \alert{Text}? In presentations \alert
[...]
> > org-export-latex-emphasis-alist (quote
> > (("*" "\\textbf{%s}" nil)
> > ("/" "\\emph{%s}" nil)
> > ("_" "\\underline{%s}" nil)
> > ("+" "\\texttt{%s}" nil)
> > ("=" "\\verb=%s=" nil)
> > ("~" "\\verb~%s~" t)
> > ("@" "\\alert{%s}" nil))))
> >
>
> That's what I'm using as well, but the problem is that it's not compatible
> anymore with non-beamer LaTeX, the alert macro being unknown.
Very true. I've never thought about this as my presentations are for
presentation only etc. However, it would definitely be nice to have a
more general solution.
> Would there be a way to conditionally translate @...@ to alert (if beamer) or
> to emph (if not-beamer), so that we can still easily compile a document to one
> or the other LaTeX "back-end", without having to customize variables in Emacs,
> prior to a compilation to the other "back-end"?
The alist structure doesn't allow for embedded lisp code, as far as I
can tell. It would obviously be easier if this structure could be
evaluated on the fly.
> I must admit I do not have clear specifications on how to tell Org about such
> a config...
The only suggestion I can come up with would be to modify this
variable using, for instance, the org-export-later-after-initial-vars-hook?
eric
next prev parent reply other threads:[~2010-01-26 17:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 19:10 [org-beamer] \alert Sven Bretfeld
2010-01-25 10:58 ` Eric S Fraga
2010-01-25 16:55 ` Sven Bretfeld
2010-01-26 15:06 ` Sébastien Vauban
2010-01-26 16:22 ` Eric S Fraga [this message]
2010-01-28 17:58 ` Carsten Dominik
2010-01-29 9:40 ` Eric S Fraga
2010-01-29 11:26 ` Tim Burt
2010-01-29 12:23 ` Eric S Fraga
2010-01-29 15:36 ` Sébastien Vauban
2010-02-01 16:18 ` Carsten Dominik
2010-02-03 8:31 ` Karsten Heymann
2010-02-03 10:21 ` Carsten Dominik
2010-02-03 22:05 ` Sven Bretfeld
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=87k4v4omyk.wl%ucecesf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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).