summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJim Meyering <meyering@fb.com>2020-12-23 09:30:19 -0800
committerJim Meyering <meyering@fb.com>2020-12-25 08:44:07 -0800
commit62f80185508ce8c59cdb99724c5cc8710c29f523 (patch)
tree6df4b375d62d1284df0581278304de2487c56709 /doc
parent91ce9cdad384cb6d774e9884707c7f00946d909d (diff)
downloadgrep-62f80185508ce8c59cdb99724c5cc8710c29f523.tar.gz
grep: use of --unix-byte-offsets (-u) now elicits a warning
* NEWS (Change in behavior): Mention this. * src/grep.c (main): Warn about each use of obsolete --unix-byte-offsets (-u). * doc/grep.in.1 (-u): Remove its documentation.
Diffstat (limited to 'doc')
-rw-r--r--doc/grep.in.114
1 files changed, 0 insertions, 14 deletions
diff --git a/doc/grep.in.1 b/doc/grep.in.1
index 3bd31310..9039c9a9 100644
--- a/doc/grep.in.1
+++ b/doc/grep.in.1
@@ -426,20 +426,6 @@ from a single file will all start at the same column,
this also causes the line number and byte offset (if present)
to be printed in a minimum size field width.
.TP
-.BR \-u ", " \-\^\-unix\-byte\-offsets
-Report Unix-style byte offsets.
-This switch causes
-.B grep
-to report byte offsets as if the file were a Unix-style text file,
-i.e., with CR characters stripped off.
-This will produce results identical to running
-.B grep
-on a Unix machine.
-This option has no effect unless
-.B \-b
-option is also used;
-it has no effect on platforms other than MS-DOS and MS-Windows.
-.TP
.BR \-Z ", " \-\^\-null
Output a zero byte (the ASCII
.B NUL