| 1 | %
|
|---|
| 2 | % LaTeX commands and macros needed for the two Distutils manuals,
|
|---|
| 3 | % inst.tex and dist.tex.
|
|---|
| 4 | %
|
|---|
| 5 | % $Id: distutils.sty 15178 2000-04-19 22:40:34Z gward $
|
|---|
| 6 | %
|
|---|
| 7 |
|
|---|
| 8 | % My gripe list about the Python style files:
|
|---|
| 9 | % * I want italics in verbatim environments for variable
|
|---|
| 10 | % text (verbatim.sty?)
|
|---|
| 11 | % * I hate escaping underscores (url.sty fixes this)
|
|---|
| 12 |
|
|---|
| 13 | % '\command' is for Distutils commands which, depending on your
|
|---|
| 14 | % perspective, are just arguments to the setup script, or sub-
|
|---|
| 15 | % commands of the setup script, or the classes that implement
|
|---|
| 16 | % each "command".
|
|---|
| 17 | \newcommand{\command}[1]{\code{#1}}
|
|---|
| 18 |
|
|---|
| 19 | % '\option' is for Distutils options *in* the setup script. Command-
|
|---|
| 20 | % line options *to* the setup script are marked up in the usual
|
|---|
| 21 | % way, ie. with '\programopt' or '\longprogramopt'
|
|---|
| 22 | \newcommand{\option}[1]{\textsf{\small{#1}}}
|
|---|
| 23 |
|
|---|
| 24 | % '\filevar' is for variable components of file/path names -- eg.
|
|---|
| 25 | % when you put 'prefix' in a pathname, you mark it up with
|
|---|
| 26 | % '\filevar' so that it still looks pathname-ish, but is
|
|---|
| 27 | % distinguished from the literal part of the path. Fred says
|
|---|
| 28 | % this can be accomplished just fine with '\var', but I violently
|
|---|
| 29 | % disagree. Pistols at dawn will sort this one out.
|
|---|
| 30 | \newcommand{\filevar}[1]{{\textsl{\filenq{#1}}}}
|
|---|
| 31 |
|
|---|
| 32 | % Just while the code and docs are still under development.
|
|---|
| 33 | \newcommand{\XXX}[1]{\textbf{**#1**}}
|
|---|
