Chet Ramey wrote:
>> Will setting pipefail have any effect on this? If not, then is there a
>> way to make bash abort when one of the pipeline components fails,
>> without too much additional code?
Not easily.
>> On the other hand, to match the documentation, you would also have to
>> fix cases
Marcin Owsiany wrote:
> On Mon, Oct 06, 2008 at 04:09:49PM -0400, Chet Ramey wrote:
>>> That's the case that's behaving correctly, even though it's not the
>>> way you want it to behave. Neither case should terminate the shell.
>>> Only a simple command should terminate the shell, and a pipeline i
On Mon, Oct 06, 2008 at 04:09:49PM -0400, Chet Ramey wrote:
> > That's the case that's behaving correctly, even though it's not the
> > way you want it to behave. Neither case should terminate the shell.
> > Only a simple command should terminate the shell, and a pipeline is
> > not a simple comma
> That's the case that's behaving correctly, even though it's not the
> way you want it to behave. Neither case should terminate the shell.
> Only a simple command should terminate the shell, and a pipeline is
> not a simple command, even if its components are. Chet is saying that
> the next bash
Marcin Owsiany <[EMAIL PROTECTED]> wrote:
> On Mon, Oct 06, 2008 at 09:22:30AM -0400, Chet Ramey wrote:
>> This bug only occurs when errexit is enabled and the final element of a
>> pipeline is a simple command that returns a non-zero exit status.
>
> Well, if the final element in the pipeline is a
On Mon, Oct 06, 2008 at 09:22:30AM -0400, Chet Ramey wrote:
> Marcin Owsiany wrote:
>
> > I expected that if a simple pipeline failure causes the shell to exit, and
> > a simple for loop failure causes it to exit, then a failure in their
> > combination would also cause an exit. However it is no
On 10/ 6/08 05:11 PM, Chet Ramey wrote:
2. What library installs the `sigacthandler'? It's not a function in
bash. It is a symbol in libc, but there's no indication which
library installs it as a signal handler.
I have just tried psig on on running bash (in another config), and see
> >
> > 2. What library installs the `sigacthandler'? It's not a function in
> > bash. It is a symbol in libc, but there's no indication which
> > library installs it as a signal handler.
> >
>
> I have just tried psig on on running bash (in another config), and see
> that the functi
Hi Chet,
thanks for the quick answer. More in-line:
On 10/ 3/08 10:52 PM, Chet Ramey wrote:
Serge Dussud - Sun Microsystems wrote:
Hello bug-bash,
please find attached a bashbug report. I am not sure how to follow-up
then, could you advise ?
This is the appropriate venue for these reports.
I was going about my business one day when I executed the following
steps in order without meaning to:
1. Caused the "Display all XXX possibilities? (y or n)" message to
appear
2. Resized the window
3. Noticed that the message disappeared, but the acceptance of y or n
(and only y or n, save ^C of
Marcin Owsiany wrote:
> I expected that if a simple pipeline failure causes the shell to exit, and a
> simple for loop failure causes it to exit, then a failure in their
> combination would also cause an exit. However it is not so.
You've found a probable bug, but it's not where you think. Eac
11 matches
Mail list logo
