Repository navigation
Improve pipeline for native commands #559
Description
Consider
ping -c 4 ya.ru | grep 64
Run it in PS and in bash. Compare UX.
In PS output of ping is collected, then it's passed down the pipe all together.
In bash you see output of grep instantly after ping send one line to the pipe.
As Bruce Payette (@BrucePay) pointed out it never appeared to be a problem on windows due to the lack of pipeable native command-line tools.
As a minimum, we should sort out this buffering flow.
Desirable: improve pipe speed for certain cases (i.e. native command to native command).
Open question: can we use a native pipe to provide a compatible speed, when pipeline doesn't involve PS commands?
Activity
21 remaining items
vors commentedon Sep 12, 2016
I'm going to narrow scope if this issue just to the first part:
For the
native | nativepart, we will use #1908vors commentedon Sep 12, 2016
Doing this work, I'm constantly having problems because of #1486
Since this change will affect a lot of code paths, I'd like to extensively run "Feature" tests locally in different systems and make sure that I don't introduce regressions. I'm considering this work blocked on #1486 and moving it to the next milestone to fix our test harness first.
joaoe commentedon Nov 24, 2019
Does the fix work for the use case with fd redirection ?
PowerShell also mangles output when redirecting file descriptors.