rexkogit...@gmx.at wrote:
This could be made a bit more consistent.
Fair enough, I installed the attached.
>From 96e100ad23ec85bf602064298bf86b22cb358525 Mon Sep 17 00:00:00 2001
From: Paul Eggert
Date: Sun, 12 Feb 2017 13:43:01 -0800
Subject: [PATCH] doc: clarify default input (Bug#25651)
*
Hello, Paul,
this is correct, it is mentioned in grep --help. However, I always
expect the man pages to be more exhaustive. But here, it only says
grep searches the named input FILEs for lines containing a match to the
given PATTERN. If no files are specified, or if the file “-” is given,
grep se
On 02/08/2017 01:12 PM, rexkogit...@gmx.at wrote:
Maybe this could be added in the man page.
It is already mentioned there, no? 'grep --help' says "With no FILE,
read . if a command-line -r is given, - otherwise." Perhaps the wording
could be improved; if so, specific wording suggestions woul
Thanks for the clearance, but this behaviour is very ... unexpected.
ps ax | grep 0:00 xyz
is clear that the second parameter is meant to be interpreted as
filename, otherwise it should read
ps ax | grep '0:00 xyz'
But I was not expecting "." instead of "-" when option -r is in use.
Maybe
On 02/07/2017 12:24 PM, rexkogit...@gmx.at wrote:
Maybe, the command line is interpreted as:
* r ... search files recursively in directories. Note, that input is
read from stdin here.
* e ... use the following pattern
* h ... this is the pattern expected by "e"
Yes, that's the in
Hello,
I could repeatedly reproduce an unexpected behaviour on several Linux
systems (two installations of Arch Linux [newest state], a Debian [8.7]
and a Ubuntu [16.4]).
I ran the following command - when I first ran it, it was accidentially
ps ax | grep -reh
I wanted to grep for processes
