home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ukma!gatech!destroyer!cs.ubc.ca!unixg.ubc.ca!msr.triumf.ca!asnd
- From: asnd@msr.triumf.ca (Donald Arseneau)
- Newsgroups: comp.text.tex
- Subject: Re: Blanks after a \newcommand!
- Date: 27 Jan 1993 18:19 PST
- Organization: TRIUMF: Tri-University Meson Facility
- Lines: 39
- Distribution: world
- Message-ID: <27JAN199318190528@msr.triumf.ca>
- References: <C1IsoM.L6D@cs.uiuc.edu>
- NNTP-Posting-Host: msr.triumf.ca
- News-Software: VAX/VMS VNEWS 1.41
-
- In article <C1IsoM.L6D@cs.uiuc.edu>, bharat@cs.uiuc.edu (R. Bharat Rao) writes...
- %
- % The points in \evec are defined by ...
- %
- % there is no space bewteen the bold "E" and the following word "are".
- %
- % I can remedy this by typing
- %
- % The points in \evec\ are defined by ..
- %
- % adding a space using "\ ". However, is there any way for me to set
- % up my command in \newcommand to do this automatically (i.e., leave
- % a space if there is a following space, else not leave a space..
- %
- % As, I do this for 50+ symbols in my thesis, it would really simplify
- % my task to avoid having to add "\ " every time...
-
- The big problem I find with using \ is that I get accidental \, and \..
- If it were easy to put something after the commands everywhere, I could
- use a global substitution in the editor.
-
- Here are two methods:
-
- 1) Put a non-letter at the end of the command name so spaces are not
- ignored:
-
- \def\Ea.{\ifmmode E_a \else $E_a$\fi}
-
- The problems are that \newcommand won't handle names with "syntax"
- and those extra characters can be confusing (would the REAL periods
- please stand up!)
-
- 2) Define the commands normally, but use them with {} after:
- \LaTeX{} is easy to use if you like the available formats,
- otherwise, you need to know the raw \TeX{}.
-
- Any others?
-
- Donald Arseneau asnd@reg.triumf.ca
-