bug-grep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH] doc: remove the statement about unrecognized options naming


From: Kir Kolyshkin
Subject: [PATCH] doc: remove the statement about unrecognized options naming
Date: Mon, 17 May 2010 18:38:12 +0400

Remove the following statement from docs (from the part with the
description of POSIXLY_CORRECT environment variable):

    Also, POSIX.2 requires that unrecognized options be diagnosed
    as “illegal”, but since they are not really against the law
    the default is to diagnose them as “invalid”.

First, this statement is wrong because grep reports about such
options as "unrecognized" whether POSIXLY_CORRECT is set or not.
Second, the error message is printed by getopt_long() from glibc,
i.e. this code is not part of grep and should not be documented here.

* doc/grep.in.1: Remove.
* doc/grep.texi: Likewise.

Signed-off-by: Kir Kolyshkin <address@hidden>
---
 doc/grep.in.1 |    3 ---
 doc/grep.texi |    4 ----
 2 files changed, 0 insertions(+), 7 deletions(-)

diff --git a/doc/grep.in.1 b/doc/grep.in.1
index cdae4d9..2433134 100644
--- a/doc/grep.in.1
+++ b/doc/grep.in.1
@@ -1130,9 +1130,6 @@ behaves more like other \s-1GNU\s0 programs.
 \s-1POSIX.2\s0 requires that options that 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, \s-1POSIX.2\s0 requires that unrecognized options be diagnosed as
-\*(lqillegal\*(rq, but since they are not really against the law the default
-is to diagnose them as \*(lqinvalid\*(rq.
 .B POSIXLY_CORRECT
 also disables \fB_\fP\fIN\fP\fB_GNU_nonoption_argv_flags_\fP,
 described below.
diff --git a/doc/grep.texi b/doc/grep.texi
index 87480de..560c648 100644
--- a/doc/grep.texi
+++ b/doc/grep.texi
@@ -935,10 +935,6 @@ 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,
address@hidden requires that unrecognized options be diagnosed as ``illegal'',
-but since they are not really against the law the default
-is to diagnose them as ``invalid''.
 @code{POSIXLY_CORRECT} also disables @address@hidden,
 described below.
 
-- 
1.6.6.1




reply via email to

[Prev in Thread] Current Thread [Next in Thread]