bug-gnu-utils
[Top][All Lists]
Advanced

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

Re: Grep man page: --line-buffering vs. --line-buffered


From: Jori Mantysalo
Subject: Re: Grep man page: --line-buffering vs. --line-buffered
Date: Wed, 28 May 2003 13:42:38 +0300 (EEST)

Paul Jarc wrote that

> I am not the grep maintainer, so you should send this to the list.

So here comes two notes and question.

I think that "flush output on every line" is easier to understand, so it
might be good idea to change description on man page to be like info
page.

Another thing, propably also typo, is

 -F, --fixed-strings
        Interpret PATTERN as a list of fixed strings, separated by new-
        lines,  any of which is to be matched.  -P, --perl-regexp Inter-
        pret PATTERN as a Perl regular expression.

I think that it should be two separated items, like

 -F, --fixed-strings
        Interpret PATTERN as a list of fixed strings, separated by new-
        lines,  any of which is to be matched.

 -P, --perl-regexp
        Interpret PATTERN as a Perl regular expression.

And last: What this default means?

 `--directories=ACTION'
      If an input file is a directory, use ACTION to process it.  By
      default, ACTION is `read', which means that directories are read
      just as if they were ordinary files (some operating systems and
      filesystems disallow this, and will cause `grep' to print error
      messages for every directory or silently skip them).

I tried "grep --directories=read "." somefile somedirectory" and I just
get contents of "somefile", not anything from "somedirectory". I am using
Linux, kernel 2.4.20, ext3 FS. Maybe man page could be clearer.

-- 
Jori Mäntysalo




reply via email to

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