From: James Harkins <jamshark70@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Rationale for *text* -> \alert{text} for Beamer export?
Date: Thu, 2 May 2013 19:44:17 +0800 [thread overview]
Message-ID: <CAFniQ7V2FBcqfrWHnNe84phv11kFNJt15d-=mFrkbK5vKL0evA@mail.gmail.com> (raw)
In-Reply-To: <87mwsdiyie.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
On May 2, 2013 4:20 PM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
> James Harkins <jamshark70@gmail.com> writes:
>
> > That would assume that you can customize the string org uses for
> > *bold*, which you can't at present... so maybe my hack has some use
> > after all.
>
> This has already been discussed, and there's a solution provided at:
>
> http://orgmode.org/worg/exporters/beamer/ox-beamer.html
>
> No need to add another customize for that. Thank you for your patch,
> though.
Fair enough -- that's far more flexible than what I did. I did the hack
months ago, when the documentation of the new exporter hadn't been written.
I never would have guessed that solution, based on the docstrings available
at the time.
FWIW, I wasn't submitting the patch for inclusion. It's only that a patch
was the easiest way to show the change. I guess I should have said so
specifically, since it's natural to assume that a patch posted to the list
is a proposal for a (permanent) change. Not my intent here.
hjh
[-- Attachment #2: Type: text/html, Size: 1398 bytes --]
next prev parent reply other threads:[~2013-05-02 11:44 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 [this message]
2013-05-02 9:53 ` Marcin Borkowski
2013-05-02 10:28 ` Suvayu Ali
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='CAFniQ7V2FBcqfrWHnNe84phv11kFNJt15d-=mFrkbK5vKL0evA@mail.gmail.com' \
--to=jamshark70@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
--cc=n.goaziou@gmail.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).