From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Rationale for *text* -> \alert{text} for Beamer export?
Date: Thu, 2 May 2013 12:28:56 +0200 [thread overview]
Message-ID: <20130502102856.GC17914@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <loom.20130502T044704-864@post.gmane.org>
On Thu, May 02, 2013 at 02:48:41AM +0000, James Harkins wrote:
> ... implemented my own hack to customize the LaTeX
> command for beamer to use for *bold text* (pasted as a git patch
> below).
[...chomp...chomp...chomp...]
> From 8ccbc7cad43b520067b8b29d4660fc99587995fd Mon Sep 17 00:00:00 2001
> From: James Harkins <jamshark70@dewdrop-world.net>
> Date: Thu, 21 Feb 2013 09:51:02 +0800
> Subject: [PATCH] hjh temp: add customize variable for bold/alert style
>
> ---
> lisp/ox-beamer.el | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/lisp/ox-beamer.el b/lisp/ox-beamer.el
> index dc427de..44c1c68 100644
> --- a/lisp/ox-beamer.el
> +++ b/lisp/ox-beamer.el
> @@ -206,6 +206,12 @@ You might want to put e.g. \"allowframebreaks=0.9\"
> here."
> :group 'org-export-beamer
> :type '(string :tag "Outline frame options"))
>
> +(defcustom org-beamer-bold-macro "alert"
> + "LaTeX macro to insert for bold text (delimited by asterisks in the org
> source file).
> +The default \"alert\" renders as red text, normal weight.
> +Substitute \"textbf\" to obtain boldface."
> + :group 'org-export-beamer
> + :type '(string :tag "Bold macro"))
>
> \f
> ;;; Internal Variables
> @@ -334,7 +340,8 @@ Return overlay specification, as a string, or nil."
> "Transcode BLOCK object into Beamer code.
> CONTENTS is the text being bold. INFO is a plist used as
> a communication channel."
> - (format "\\alert%s{%s}"
> + (format "\\%s%s{%s}"
> + org-beamer-bold-macro
> (or (org-beamer--element-has-overlay-p bold) "")
> contents))
Not sure a patch introducing yet another variable is warranted when all
you need is a filter:
<http://orgmode.org/worg/exporters/beamer/ox-beamer.html#export-filters>
--
Suvayu
Open source is the future. It sets us free.
prev parent reply other threads:[~2013-05-02 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 14:17 Rationale for *text* -> \alert{text} for Beamer export? John Hendy
2013-05-01 15:00 ` Marcin Borkowski
2013-05-01 20:50 ` John Hendy
2013-05-01 21:41 ` Thomas S. Dye
2013-05-01 22:09 ` Marcin Borkowski
2013-05-02 10:44 ` Suvayu Ali
2013-05-02 2:48 ` James Harkins
2013-05-02 8:20 ` Nicolas Goaziou
2013-05-02 11:44 ` James Harkins
2013-05-02 9:53 ` Marcin Borkowski
2013-05-02 10:28 ` Suvayu Ali [this message]
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=20130502102856.GC17914@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@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).