[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ls: write error: Broken pipe
From: |
Jim Meyering |
Subject: |
Re: ls: write error: Broken pipe |
Date: |
Fri, 02 Nov 2007 18:45:36 +0100 |
Dan Nicolaescu <address@hidden> wrote:
> This is probably not the right place to talk about this, but since you
> started...
:-)
> bash didn't have decent programmable completion until 3.0 (maybe
That was one of the reasons I switched to zsh.
> 3.1?). It still does not have dabbrev-expand, which for someone used
> to emacs is irreplaceable. (Yes, I did submit a patch, it will be
> available in the next version of bash). There's a few other missing
> things: the prompt ellipsis, run-fg-editor,
I don't know what those are, sorry.
> zsh is a non-starter, it is not available on many systems that I have
> to use.
If it wasn't around, and couldn't be installed, I've
always just built a private version and made whatever
shell happened to be the default "exec" it.
> I am pretty happy with tcsh, the only problem is that some systems
> don't install it by default anymore.
>
> > Lack of a decent signal-handling mechanism is one of them.
>
> This has never been a problem for my use.
Before now, of course :-)
> > > whether to catch SIGPIPE or not. Maybe something has changed in tcsh
> > > to make it catch SIGPIPE...
> >
> > How do you start tcsh?
>
> It's the login shell. I used it in xterm, not sure how xterm starts
> it.
Look at pstree output to see which program starts your xterm,
then see if that parent or some ancestor script uses "trap".
Just searching for "grep -w trap ~/.??" might give you something
interesting.
Either your version of tcsh is somehow different from mine,
or some parent process is catching SIGPIPE.
- ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/01
- Re: ls: write error: Broken pipe, Paul Eggert, 2007/11/01
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/01
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/02
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/02
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/02
- Re: ls: write error: Broken pipe,
Jim Meyering <=
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/08
- Re: ls: write error: Broken pipe, Paul Eggert, 2007/11/08
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/09
- Re: ls: write error: Broken pipe, Bob Proulx, 2007/11/09
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/09
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/09
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/09
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/09
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/09
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/09