[bug #14630] feature request: grep -p[separator]

[Charles Levert]

Update of bug #14630 (project grep):

                Severity:              3 - Normal => 1 - Wish               

    _______________________________________________________

Follow-up Comment #1:

"Shocked" sounds somewhat quite strong a word.  It's not so surprising that a
non-standard extension which can readily be replicated with common existing
tools is not implemented in GNU grep.

/sbin/ifconfig -a | awk 'BEGIN {RS = "\n\n"} /127/'
/sbin/ifconfig -a | perl -ne 'BEGIN {$/ = "\n\n"} print if /127/'

Even with its four superfluous spaces characters, the awk solution is even
shorter than, say

/sbin/ifconfig -a | grep --input-record-separator='\n\n' 127

given that awk and perl also support an output record separator, which
someone would invariably ask to be supported as well with its own distinctive
option, sooner or later.

It's easy enough to define a shell function or minimal awk/perl script around
either of the two basic one-line templates above.

Do we really need to add this to GNU grep?


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=14630>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/