summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>1997-12-16 14:43:37 (GMT)
committerFred Drake <fdrake@acm.org>1997-12-16 14:43:37 (GMT)
commit9d2f7d414d2173ffb5b746e6ba365ab9c607a305 (patch)
tree46dfb97e7393929136fa5b8b1ff0fb4d1ddf1d76 /Doc
parent5493205ba4a5c8f01266db0adfbb87dd616b0690 (diff)
downloadcpython-9d2f7d414d2173ffb5b746e6ba365ab9c607a305.zip
cpython-9d2f7d414d2173ffb5b746e6ba365ab9c607a305.tar.gz
cpython-9d2f7d414d2173ffb5b746e6ba365ab9c607a305.tar.bz2
Oops, ".pythonrc.py" should *always* be marked with \file{}; one occurrance
escaped with \var{}.
Diffstat (limited to 'Doc')
-rw-r--r--Doc/lib/libuser.tex2
-rw-r--r--Doc/libuser.tex2
2 files changed, 2 insertions, 2 deletions
diff --git a/Doc/lib/libuser.tex b/Doc/lib/libuser.tex
index 778ca7e..39daf97 100644
--- a/Doc/lib/libuser.tex
+++ b/Doc/lib/libuser.tex
@@ -35,7 +35,7 @@ generally not a good idea.
A suggestion for programmers who wish to use this mechanism: a simple
way to let users specify options for your package is to have them
-define variables in their \var{.pythonrc.py} file that you test in
+define variables in their \file{.pythonrc.py} file that you test in
your module. For example, a module \code{spam} that has a verbosity
level can look for a variable \code{user.spam_verbose}, as follows:
diff --git a/Doc/libuser.tex b/Doc/libuser.tex
index 778ca7e..39daf97 100644
--- a/Doc/libuser.tex
+++ b/Doc/libuser.tex
@@ -35,7 +35,7 @@ generally not a good idea.
A suggestion for programmers who wish to use this mechanism: a simple
way to let users specify options for your package is to have them
-define variables in their \var{.pythonrc.py} file that you test in
+define variables in their \file{.pythonrc.py} file that you test in
your module. For example, a module \code{spam} that has a verbosity
level can look for a variable \code{user.spam_verbose}, as follows: