Update of bug #13225 (project grep):
Status: None => Invalid
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
I guess you are piping standard output from another command into Grep, and
you expect both Grep and the other command to run in parallel and stop as
soon as Grep finds the specified match. In Windows (at least the older
versions that I am familiar with) pipes are handled by running the first
command, storing its output, and then, after that command is finished,
running the second command, feeding it the stored data. Thus you have to
wait for the first command to finish before Grep can do its work. This is
not a bug in Grep, but just a "feature" of Windows.
If you disagree, please re-open this bug report and state exactly what
command you used in such a way that we can reproduce the effect, and state
what version of Windows you are using and what shell (command.com, cmd.exe,
Cygwin Bash, etc.).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=13225>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
