Jim Meyering <[EMAIL PROTECTED]> writes: > Dan Nicolaescu <[EMAIL PROTECTED]> wrote: > > I have been using this alias: lt = 'ls -lt | head' > ... > > ls: write error: Broken pipe > > > > Is there any reason for this error to be printed? > > Hi Dan, > > You should see it only if you have changed the default signal > handling to ignore SIGPIPE, and then only some of the time. > When it's possible to see it, kernel buffering and the size of your > environment also determine how much can be written before the > signal is sent.
Hmm, that probably explains the behavior I am seeing: in the beginning no error, but after executing a few commands (i.e. the history size grows) This is with tcsh, and AFAIK tcsh does not have a way to tell it whether to catch SIGPIPE or not. Maybe something has changed in tcsh to make it catch SIGPIPE... > This topic was beaten to death as a side effect of my patch to > make git detect a bunch of previously-ignored write errors: > > http://thread.gmane.org/gmane.comp.version-control.git/48469/focus=48617 > > If you're bored, read on in that thread... it gets even more animated. Sorry, I don't know about this... (and I don't have time to read a very long thread). _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
