Return system configuration information relevant to an open file.
\var{name} specifies the configuration value to retrieve; it may be a
string which is the name of a defined system value; these names are
-specified in a number of standards (\POSIX.1, \UNIX 95, \UNIX 98, and
+specified in a number of standards (\POSIX.1, \UNIX{} 95, \UNIX{} 98, and
others). Some platforms define additional names as well. The names
known to the host operating system are given in the
\code{pathconf_names} dictionary. For configuration variables not
Return system configuration information relevant to a named file.
\var{name} specifies the configuration value to retrieve; it may be a
string which is the name of a defined system value; these names are
-specified in a number of standards (\POSIX.1, \UNIX 95, \UNIX 98, and
+specified in a number of standards (\POSIX.1, \UNIX{} 95, \UNIX{} 98, and
others). Some platforms define additional names as well. The names
known to the host operating system are given in the
\code{pathconf_names} dictionary. For configuration variables not
of its subdirectories (directories are generated bottom up).
When \var{topdown} is true, the caller can modify the \var{dirnames} list
-in-place (e.g., via \keyword{del} or slice assignment), and
+in-place (perhaps unsing \keyword{del} or slice assignment), and
\function{walk()} will only recurse into the subdirectories whose names
remain in \var{dirnames}; this can be used to prune the search,
impose a specific order of visiting, or even to inform \function{walk()}
Return string-valued system configuration values.
\var{name} specifies the configuration value to retrieve; it may be a
string which is the name of a defined system value; these names are
-specified in a number of standards (\POSIX, \UNIX 95, \UNIX 98, and
+specified in a number of standards (\POSIX, \UNIX{} 95, \UNIX{} 98, and
others). Some platforms define additional names as well. The names
known to the host operating system are given in the
\code{confstr_names} dictionary. For configuration variables not
separating items with commas: \code{[a, b, c]}. Tuples are
constructed by the comma operator (not within square brackets), with
or without enclosing parentheses, but an empty tuple must have the
-enclosing parentheses, e.g., \code{a, b, c} or \code{()}. A single
-item tuple must have a trailing comma, e.g., \code{(d,)}.
+enclosing parentheses, such as \code{a, b, c} or \code{()}. A single
+item tuple must have a trailing comma, such as \code{(d,)}.
\obindex{sequence}
\obindex{string}
\obindex{Unicode}
include that file may remain unchanged, increase to the specified
size as if zero-filled, or increase to the specified size with
undefined new content.
- Availability: Windows, many \UNIX variants.
+ Availability: Windows, many \UNIX{} variants.
\end{methoddesc}
\begin{methoddesc}[file]{write}{str}