[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: EMBARRASING! [Broken Pipe problem - Again...]
From: |
Torben Wölm |
Subject: |
RE: EMBARRASING! [Broken Pipe problem - Again...] |
Date: |
Sat, 17 Feb 2001 14:40:28 +0100 |
I am so sorry!
There never was a problem in Bash.
It turned out that the problem is that I'm a guy with a hand coordination
problem and an international keyboard!
For those of you who want to enjoy my total embarrasment:
In order to type the pipe-symbol I have to hold my "Alt Gr"-key. And because
my hands are not that well coordinated, I sometimes do not release the "Alt
Gr"-key before typing the space following the pipe symbol! And the space
then is somehow discarded which in turn gives the error...
I'm sorry for wasting your time!
Regards
Torben
> -----Original Message-----
> From: Torben Wölm [SMTP:torben.wolm@europe.lego.com]
> Sent: Saturday, February 17, 2001 10:02 AM
> To: 'bug-bash@gnu.org'
> Subject: RE: Broken Pipe problem - Again...
>
> BTW:
>
> I'm running Red Hat Linux 6.1.
>
> I upgraded bash to 2.04 to see if that helped. I also upgraded my kernel
> to
> 2.4.1, but the problem is still there.
>
> Anybody with the same problem?
>
> It is really annoying! Not being able to use pipes is like watching the
> Late
> Show without David Letterman!
>
> /Torben
>
> > -----Original Message-----
> > From: Torben Wölm [SMTP:torben.wolm@europe.lego.com]
> > Sent: Thursday, February 15, 2001 1:07 PM
> > To: 'bug-bash@gnu.org'
> > Subject: Broken Pipe problem - Again...
> >
> > Hi.
> >
> > I have a problem with pipes in Bash.
> >
> > If I write for instance:
> >
> > $ rpm -q -a | fgrep "bash"
> >
> > I sometimes get a pipe broken error message and "fgrep: command not
> found"
> >
> > If I run "rpm -q -a" one or more times without the pipe, and then try
> > again
> > with the pipe, it works!
> >
> > (BTW: Running fgrep by itself works fine...)
> >
> > I've recompiled Bash according to the FAQ regarding SIGPIPE. And that's
> > fine. Now I don't get the "pipe broken" error message anymore. But I
> don't
> > get any output besides "fgrep: command not found".
> >
>
> _______________________________________________
> Bug-bash mailing list
> Bug-bash@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-bash
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- RE: EMBARRASING! [Broken Pipe problem - Again...],
Torben Wölm <=