|
From: | Linda Walsh |
Subject: | Re: bash giving wrong message for indicated failure (was Re: Unhelpful behaviors in 4.2.10(1)) |
Date: | Thu, 14 Jun 2012 11:40:12 -0700 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.24) Gecko/20100228 Lightning/0.9 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666 |
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.
----- Erp....details!.... ;-) Maybe the error message could be included with bash? It's a nice feature to have builtin...(if it works correctly)...
[Prev in Thread] | Current Thread | [Next in Thread] |