From: "Pepe Barbe" <elventear@gmail.com>
Subject: Re: \definesomething?
Date: Sat, 26 Aug 2006 22:32:02 -0500 [thread overview]
Message-ID: <3e73596b0608262032y255be8d8oefc433604ae774ac@mail.gmail.com> (raw)
In-Reply-To: <Pine.WNT.4.63.0608252350430.1256@nqvgln>
On 8/25/06, Aditya Mahajan <adityam@umich.edu> wrote:
> \define\mymacro#1 is equivalent to
>
> \def\mymacro#1 but also checks if mymacro has already been defined.
Thanks for the info. I am using \define for something simple, define
some keywords with special format that I will be repeating a lot.
Something like:
\define\mybi{\bf\sl BoldItalic}
Works fin except that if I use in a sentence like: This is \mybi word.
It wil be typeset without any space between BoldItalic and word, like
this: This is my BoldItalicword.
Any ideas on how to overcome this?
Thanks,
Pepe
next prev parent reply other threads:[~2006-08-27 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 0:09 \definesomething? Pepe Barbe
2006-08-26 4:16 ` \definesomething? Aditya Mahajan
2006-08-27 3:32 ` Pepe Barbe [this message]
2006-08-27 4:04 ` \definesomething? Mojca Miklavec
2006-08-27 4:19 ` \definesomething? Aditya Mahajan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e73596b0608262032y255be8d8oefc433604ae774ac@mail.gmail.com \
--to=elventear@gmail.com \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).