[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Changes to grep/manual/html_node/Other-Options.html,v
|
From: |
Jim Meyering |
|
Subject: |
Changes to grep/manual/html_node/Other-Options.html,v |
|
Date: |
Sun, 30 Dec 2018 01:24:24 -0500 (EST) |
CVSROOT: /webcvs/grep
Module name: grep
Changes by: Jim Meyering <meyering> 18/12/30 01:24:22
Index: html_node/Other-Options.html
===================================================================
RCS file: /webcvs/grep/grep/manual/html_node/Other-Options.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- html_node/Other-Options.html 10 Feb 2017 04:43:38 -0000 1.28
+++ html_node/Other-Options.html 30 Dec 2018 06:24:22 -0000 1.29
@@ -2,7 +2,7 @@
<html>
<!-- This manual is for grep, a pattern matching engine.
-Copyright (C) 1999-2002, 2005, 2008-2017 Free Software Foundation,
+Copyright (C) 1999-2002, 2005, 2008-2018 Free Software Foundation,
Inc.
Permission is granted to copy, distribute and/or modify this document
@@ -11,16 +11,16 @@
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License". -->
-<!-- Created by GNU Texinfo 6.3, http://www.gnu.org/software/texinfo/ -->
+<!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ -->
<head>
-<title>GNU Grep 3.0: Other Options</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Other Options (GNU Grep 3.3)</title>
-<meta name="description" content="GNU Grep 3.0: Other Options">
-<meta name="keywords" content="GNU Grep 3.0: Other Options">
+<meta name="description" content="Other Options (GNU Grep 3.3)">
+<meta name="keywords" content="Other Options (GNU Grep 3.3)">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="Index.html#Index" rel="index" title="Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
@@ -70,6 +70,15 @@
<h4 class="subsection">2.1.7 Other Options</h4>
<dl compact="compact">
+<dt><samp>--</samp></dt>
+<dd><a name="index-_002d_002d"></a>
+<a name="index-option-delimiter"></a>
+<p>Delimit the option list. Later arguments, if any, are treated as
+operands even if they begin with ‘<samp>-</samp>’. For example,
‘<samp>grep PAT --
+-file1 file2</samp>’ searches for the pattern PAT in the files named
<samp>-file1</samp>
+and <samp>file2</samp>.
+</p>
+</dd>
<dt><samp>--line-buffered</samp></dt>
<dd><a name="index-_002d_002dline_002dbuffered"></a>
<a name="index-line-buffering"></a>
@@ -81,21 +90,27 @@
<dt><samp>--binary</samp></dt>
<dd><a name="index-_002dU"></a>
<a name="index-_002d_002dbinary"></a>
-<a name="index-MS_002dDOS_002fMS_002dWindows-binary-files"></a>
-<a name="index-binary-files_002c-MS_002dDOS_002fMS_002dWindows"></a>
-<p>Treat the file(s) as binary.
-By default, under MS-DOS and MS-Windows,
-<code>grep</code> guesses whether a file is text or binary
-as described for the <samp>--binary-files</samp> option.
-If <code>grep</code> decides the file is a text file,
-it strips carriage returns from the original file contents
-(to make regular expressions with <code>^</code> and <code>$</code> work
correctly).
-Specifying <samp>-U</samp> overrules this guesswork,
-causing all files to be read and passed to the matching mechanism verbatim;
-if the file is a text file with <code>CR/LF</code> pairs at the end of each
line,
-this will cause some regular expressions to fail.
-This option has no effect
-on platforms other than MS-DOS and MS-Windows.
+<a name="index-MS_002dWindows-binary-I_002fO"></a>
+<a name="index-binary-I_002fO"></a>
+<p>On platforms that distinguish between text and binary I/O,
+use the latter when reading and writing files other
+than the user’s terminal, so that all input bytes are read and written
+as-is. This overrides the default behavior where <code>grep</code>
+follows the operating system’s advice whether to use text or binary
+I/O. On MS-Windows when <code>grep</code> uses text I/O it reads a
+carriage return–newline pair as a newline and a Control-Z as
+end-of-file, and it writes a newline as a carriage return–newline
+pair.
+</p>
+<p>When using text I/O <samp>--byte-offset</samp> (<samp>-b</samp>) counts and
+<samp>--binary-files</samp> heuristics apply to input data after text-I/O
+processing. Also, the <samp>--binary-files</samp> heuristics need not agree
+with the <samp>--binary</samp> option; that is, they may treat the data as
+text even if <samp>--binary</samp> is given, or vice versa.
+See <a
href="File-and-Directory-Selection.html#File-and-Directory-Selection">File and
Directory Selection</a>.
+</p>
+<p>This option has no effect on GNU and other POSIX-compatible platforms,
+which do not distinguish text from binary I/O.
</p>
</dd>
<dt><samp>-z</samp></dt>
@@ -112,6 +127,11 @@
</dd>
</dl>
+<hr>
+<div class="header">
+<p>
+Previous: <a
href="File-and-Directory-Selection.html#File-and-Directory-Selection"
accesskey="p" rel="prev">File and Directory Selection</a>, Up: <a
href="Command_002dline-Options.html#Command_002dline-Options" accesskey="u"
rel="up">Command-line Options</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- Changes to grep/manual/html_node/Other-Options.html,v,
Jim Meyering <=