On 11/20/16, Paul Eggert wrote:
> The man page says that -z is about "input and output data",
The man page that ships with grep 2.25 says about -z, in its entirety:
Treat the input as a set of lines, each terminated by a zero
byte (the ASCII NUL character) instead of a newline. Like t
vampyre...@gmail.com wrote:
I only looked at the man page for -z.
Sorry, I'm still not seeing a problem. The man page says that -z is about "input
and output data", and -o causes output data to be generated. Maybe you were
looking at an older version of the manual? If not, could you please ci
On 11/19/16, Paul Eggert wrote:
> vampyre...@gmail.com wrote:
>> The documentation also states that -z affects only how input is
>> interpreted.
>
> I don't see where it does that, as the current documentation for -z talks
> about
> both "input and output data".
Ah, the pitfalls of multiple for
vampyre...@gmail.com wrote:
The documentation also states that -z affects only how input is interpreted.
I don't see where it does that, as the current documentation for -z talks about
both "input and output data". That being said, the manual could be clearer. I
installed the attached.
From 4
This bug report concerns GNU grep 2.25.
Consider this file:
$ cat test
one lone
long
tone
"grep -o", according to the man page and info file, outputs "each [matched]
part on a separate output line." Given that, this command gives the expected
output:
$ grep -o one test
one
one
one
The docum
