[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bash giving wrong message for indicated failure (was Re: Unhelpful b
From: |
Chet Ramey |
Subject: |
Re: bash giving wrong message for indicated failure (was Re: Unhelpful behaviors in 4.2.10(1)) |
Date: |
Thu, 14 Jun 2012 08:35:01 -0400 |
> > That's fine -- if the error message points at the included file as "not
> > returning a > 'true' value.
> >
> > It doesn't. It points to a conditional in the previous file.
Note that the error message wasn't generated by bash: you generated it
yourself based on $BASH_COMMAND and the various LINENO variables. That
implies where information needs to be saved and restored around calls
to eval/./source.
That can be fixed, and will be for the next bash release.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
- Unhelpful behaviors in 4.2.10(1), Linda Walsh, 2012/06/08
- Re: Unhelpful behaviors in 4.2.10(1), Pierre Gaston, 2012/06/09
- Re: Unhelpful behaviors in 4.2.10(1), Linda Walsh, 2012/06/09
- Re: Unhelpful behaviors in 4.2.10(1), Pierre Gaston, 2012/06/09
- Re: Unhelpful behaviors in 4.2.10(1), Chet Ramey, 2012/06/09
- Re: Unhelpful behaviors in 4.2.10(1), Linda Walsh, 2012/06/09
- Re: bash giving wrong message for indicated failure (was Re: Unhelpful behaviors in 4.2.10(1)), Linda Walsh, 2012/06/13
- Re: bash giving wrong message for indicated failure (was Re: Unhelpful behaviors in 4.2.10(1)),
Chet Ramey <=
- Re: bash giving wrong message for indicated failure (was Re: Unhelpful behaviors in 4.2.10(1)), Linda Walsh, 2012/06/14