Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 822a86a

Browse files
committed
Trying to placate Fred: redefine \tilde and \bslash; document everything.
Still some not-quite-standard definitions in here that I have to fix.
1 parent d5faa7e commit 822a86a

1 file changed

Lines changed: 23 additions & 9 deletions

File tree

Doc/texinputs/distutils.sty

Lines changed: 23 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,21 +6,35 @@
66
%
77

88
% My gripe list about the Python style files:
9-
% * I want italics in verbatim environments (verbatim.sty?)
9+
% * I want italics in verbatim environments for variable
10+
% text (verbatim.sty?)
1011
% * I hate escaping underscores (url.sty fixes this)
1112

12-
% Should these be added to the standard Python doc tools? (They'll be
13-
% needed for my "Distributing Python Modules" guide, too.)
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".
1417
\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'
1522
\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.
1630
\newcommand{\filevar}[1]{{\textsl{\filenq{#1}}}}
17-
\newcommand{\homefile}[1]{\file{\tilde/#1}}
18-
\newcommand{\comingsoon}{\emph{Coming soon...}}
31+
1932
\def\package{\module}
2033

21-
% And how about these? Very handy for writing pathnames (tilde for
22-
% Unix, backslash for DOS/Windows).
23-
\renewcommand{\tilde}{\raisebox{-0.5ex}{\symbol{126}}}
24-
\newcommand{\bslash}{\symbol{92}} % XXX only works in tt fonts!
34+
% These two are handy for writing pathnames for Unix and Windows
35+
% (respectively). I define my own macros because I'm a lazy typist.
36+
\renewcommand{\tilde}{\textasciitilde}
37+
\newcommand{\bslash}{\textbackslash}
2538

39+
% Just while the code and docs are still under development.
2640
\newcommand{\XXX}[1]{\textbf{**#1**}}

0 commit comments

Comments
 (0)