>> 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.
Yessss.... Hm. Let's examine it from this point of view: how many - and which - use cases would break if all readers going away produced an immediate SIGPIPE to anyone with the write end still open (ie, not waiting for anything to be written)? With pipes, I can't think of any offhand, but I've put only maybe a minute's thought into it. (For network connections, well, I routinely use TCP connections with one direction shut down, so I have plenty of use cases that would break if that were extended to TCP. AF_LOCAL SOCK_STREAM socketpairs...would be up for discussion separately, I'd say.) /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML [email protected] / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
