Re: Proposed new feature for bash: unbuffered pipes, part 1: overview

2020-04-22 Thread Dale R. Worley
Greg Wooledge writes: > On Tue, Apr 21, 2020 at 08:38:41PM -0400, Dale R. Worley wrote: >> The "unbuffered pipe" symbol ">|>" causes Bash to set in the >> environment of the "grep" process a variable "STDOUT_UNBUFFERED" with >> a value that contains the dev and ino values for the pipe which the >>

Re: Proposed new feature for bash: unbuffered pipes, part 1: overview

2020-04-22 Thread Greg Wooledge
On Tue, Apr 21, 2020 at 08:38:41PM -0400, Dale R. Worley wrote: > The "unbuffered pipe" symbol ">|>" causes Bash to set in the > environment of the "grep" process a variable "STDOUT_UNBUFFERED" with > a value that contains the dev and ino values for the pipe which the > "grep" process sees as fd 1.

Proposed new feature for bash: unbuffered pipes, part 1: overview

2020-04-21 Thread Dale R. Worley
It may seem intemperate to propose that a program with an 82-page manual "page" could benefit from yet another feature, but that is what this is doing: Bash's users would benefit from a feature that suppresses buffering of output sent to particular pipes (designated by the user). At the bottom of