Re: bash giving wrong message for indicated failure (was Re: Unhelpful behaviors in 4.2.10(1))
> > 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, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/
Re: bash giving wrong message for indicated failure (was Re: Unhelpful behaviors in 4.2.10(1))
Chet Ramey wrote: 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. - Erpdetails! ;-) Maybe the error message could be included with bash? It's a nice feature to have builtin...(if it works correctly)...
