> Indeed, in which case that could be true for all pipelines, regardless > of whether the final (or some) reader is terminated by normal user > interaction or whether it is some other early algorithm driven > termination. The pager can't tell, only the feed knows whether it makes sense to decode the next block or retrieve the next commit message when the pager's gone. And for that to work, it needs what riastradh@ was asking for.
- SIGPIPE-equivalent before writing? Taylor R Campbell
- Re: SIGPIPE-equivalent before writin... Adrian Chadd
- Re: SIGPIPE-equivalent before wr... Taylor R Campbell
- Re: SIGPIPE-equivalent befor... Greg Troxel
- Re: SIGPIPE-equivalent before writin... Mouse
- Re: SIGPIPE-equivalent before writin... Greg A. Woods
- Re: SIGPIPE-equivalent before wr... Edgar Fuß
- Re: SIGPIPE-equivalent befor... Greg A. Woods
- Re: SIGPIPE-equivalent b... Edgar Fuß
- Re: SIGPIPE-equival... Mouse
- Re: SIGPIPE-equ... Edgar Fuß
- Re: SIGPIPE... Mouse
- Re: SIGPIPE... Johnny Billquist
- Re: SIGPIPE... Mouse
- Re: SIGPIPE... od2uvb
- Re: SIGPIPE... Lyndon Nerenberg (VE7TFX/VE6BBM)
- Re: SIGPIPE... Greg A. Woods
- Re: SIGPIPE... Lyndon Nerenberg (VE7TFX/VE6BBM)
- Re: [PATCH] SIGPIPE-equivalent befor... Taylor R Campbell
