From: Fred Drake Date: Tue, 16 Dec 1997 14:43:37 +0000 (+0000) Subject: Oops, ".pythonrc.py" should *always* be marked with \file{}; one occurrance X-Git-Tag: v1.5~137 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9d2f7d414d2173ffb5b746e6ba365ab9c607a305;p=python Oops, ".pythonrc.py" should *always* be marked with \file{}; one occurrance escaped with \var{}. --- diff --git a/Doc/lib/libuser.tex b/Doc/lib/libuser.tex index 778ca7e19a..39daf978c1 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 778ca7e19a..39daf978c1 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: