[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sr #104327] Flag for unmatched output to stderr?
From: |
Julian Foad |
Subject: |
[sr #104327] Flag for unmatched output to stderr? |
Date: |
Mon, 13 Jun 2005 10:52:32 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b) Gecko/20050217 |
Update of sr #104327 (project grep):
Status: None => Wont Do
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
Thanks for the idea, and I can see why you would want it in some cases, but it
just doesn't fit the general philosophy of command-line tools like Grep. The
standard error stream is for error messages or at least notifications, not for
general output. Sending unmatched lines to another destination such as a
named file would get around that problem, but there are others.
You should use a different tool such as Awk, or run two Grep commands, one
with "-v" (invert the sense of matching).
Also, be aware that Grep is not in a good position to accept new features this
year.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?func=detailitem&item_id=104327>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/