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