emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: tcburt@rochester.rr.com
Cc: emacs-orgmode@gnu.org, "n Vauban" <wxhgmqzgwmuf@spammotel.com>,
	"Carsten Dominik" <carsten.dominik@gmail.com>
Subject: Re: Re: [org-beamer] \alert
Date: Fri, 29 Jan 2010 12:23:32 +0000	[thread overview]
Message-ID: <87aavxrtff.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <19298.50653.520318.554207@nitrogen.burtket>

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.

[...]

> I hope this is of use,
> Tim

Thanks Tim.  Very helpful indeed!  

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=.
Alternatively, something like this also works:

#+latex_header: \ifx\alert\undefined\newcommand*{\alert}[1]{\textbf{#1}}\fi

in case one wants more control (e.g. could also change the colour to red).

eric

  reply	other threads:[~2010-01-29 12:23 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 [this message]
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=87aavxrtff.wl%ucecesf@ucl.ac.uk \
    --to=ucecesf@ucl.ac.uk \
    --cc=carsten.dominik@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=tcburt@rochester.rr.com \
    --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).