From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [org-beamer] \alert
Date: Mon, 1 Feb 2010 17:18:39 +0100 [thread overview]
Message-ID: <67C523EF-35DE-4180-8C0B-8DD4D0FEE9FD@gmail.com> (raw)
In-Reply-To: <87vdek53e8.fsf@mundaneum.com>
On Jan 29, 2010, at 4:36 PM, Sébastien Vauban wrote:
> Hi Eric, Tim, Carsten and all,
>
> Eric S Fraga wrote:
>> At Fri, 29 Jan 2010 06:26:21 -0500, Tim Burt wrote:
>>> Eric S Fraga writes:
>>>> For any LaTeX expert out there, is there an easy way to determine
>>>> whether
>>>> a particular macro has been defined? If so, we wouldn't even need
>>>> to check
>>>> for beamer, simply for \alert.
>>>
>>> Use the
>>> \ifx<command>\undefined ... \else ... \fi
>>> construct to determine if a command already exists, and then to
>>> take action
>>> in the appropriate case. Test the example below both as-is and
>>> with the
>>> first ~\newcommand*{\thisalert}~ commented out to see the different
>>> results.
>
> Thanks to all. This is great stuff...
>
>
>> The following org-mode line does the job for me:
>>
>> #+latex_header: \ifx\alert\undefined\let\alert\textbf\fi
>>
>> If \alert is not defined, I have =alert= behave as =textbf=.
>
> Could this somehow made part of Org-mode, so that one does not need
> to repeat
> this one-liner in every file that could be exported to pure LaTeX
> and/or
> Beamer?
Yes - this is in there now. Let's see if someone complains.
- Carsten
next prev parent reply other threads:[~2010-02-01 17:12 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
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 [this message]
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=67C523EF-35DE-4180-8C0B-8DD4D0FEE9FD@gmail.com \
--to=carsten.dominik@gmail.com \
--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).