Hi,
In doc/grep.texi some environment variables are marked with
@code{} instead of @env{}. Attached patch fixes this.
There are some other env vars that still use @code{}, but
they refer to a "category" -- I don't quite know whether
these should be marked differently too, so I have left
them alone.
Benno
--
http://www.fastmail.fm - A no graphics, no pop-ups email service
From aaf776078e8d71abd68b5246d91ded9352316947 Mon Sep 17 00:00:00 2001
From: Benno Schulenberg <bensb...@justemail.net>
Date: Sun, 3 Aug 2014 20:25:03 +0200
Subject: [PATCH] doc: mark up some environment variables as such
* doc/grep.texi (Environment Variables, and some other sections):
Use @env{} instead of @code{} for some environment variables.
---
doc/grep.texi | 12 ++++++------
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc/grep.texi b/doc/grep.texi
index 0115560..2685e59 100644
--- a/doc/grep.texi
+++ b/doc/grep.texi
@@ -816,7 +816,7 @@ the @code{terminfo} library.
@cindex default options environment variable
This variable specifies default options to be placed in front of any
explicit options.
-For example, if @code{GREP_OPTIONS} is
+For example, if @env{GREP_OPTIONS} is
@samp{--binary-files=without-match --directories=skip}, @command{grep}
behaves as if the two options @samp{--binary-files=without-match} and
@samp{--directories=skip} had been specified before
@@ -826,12 +826,12 @@ whitespace.
A backslash escapes the next character, so it can be used to
specify an option containing whitespace or a backslash.
-The @code{GREP_OPTIONS} value does not affect whether @command{grep}
+The @env{GREP_OPTIONS} value does not affect whether @command{grep}
without file operands searches standard input or the working
directory; that is affected only by command-line options. For
example, the command @samp{grep PAT} searches standard input and the
command @samp{grep -r PAT} searches the working directory, regardless
-of whether @code{GREP_OPTIONS} contains @option{-r}.
+of whether @env{GREP_OPTIONS} contains @option{-r}.
@item GREP_COLOR
@vindex GREP_COLOR @r{environment variable}
@@ -1002,7 +1002,7 @@ follow file names must be treated as file names;
by default,
such options are permuted to the front of the operand list
and are treated as options.
-Also, @code{POSIXLY_CORRECT} disables special handling of an
+Also, @env{POSIXLY_CORRECT} disables special handling of an
invalid bracket expression. @xref{invalid-bracket-expr}.
@item _@var{N}_GNU_nonoption_argv_flags_
@@ -1015,7 +1015,7 @@ A shell can put this variable in the environment for each command it runs,
specifying which operands are the results of file name wildcard expansion
and therefore should not be treated as options.
This behavior is available only with the GNU C library,
-and only when @code{POSIXLY_CORRECT} is not set.
+and only when @env{POSIXLY_CORRECT} is not set.
@end table
@@ -1343,7 +1343,7 @@ If you mistakenly omit the outer brackets, and search for say, @samp{[:upper:]},
GNU @command{grep} prints a diagnostic and exits with status 2, on
the assumption that you did not intend to search for the nominally
equivalent regular expression: @samp{[:epru]}.
-Set the @code{POSIXLY_CORRECT} environment variable to disable this feature.
+Set the @env{POSIXLY_CORRECT} environment variable to disable this feature.
Most meta-characters lose their special meaning inside bracket expressions.
--
1.7.0.4
