Bob,
'set -e' is a double-edged sword, for sure, but I'm not sure it creates
more problems than it solves. Hidden non-zero exits have wasted far more
time, for me, than this little exercise has.
On Sun, Dec 24, 2017 at 11:45 AM, Bob Proulx wrote:
> Kevin Layer wrote:
> > It took me hours of wo
Kevin Layer wrote:
> It took me hours of work to distill this down from a very large and long
> running script.
> set -eu
Hours and hours of debug time could be saved if people stopped using
'set -e' in their programs. It creates more problems than people
think it solves. Do not meddle in the a
On Fri, Dec 22, 2017 at 10:56:18AM -0800, Kevin Layer wrote:
> The man page says:
>
> The shell does not exit if the command that fails is part of the
> command list immediately following a while or until keyword,
> part of the test following the if or elif reserved words,
On 12/22/17 1:56 PM, Kevin Layer wrote:
> The man page says:
>
> The shell does not exit if the command that fails is part of the
> command list immediately following a while or until keyword,
> part of the test following the if or elif reserved words,
> part of any co
The man page says:
The shell does not exit if the command that fails is part of the
command list immediately following a while or until keyword,
part of the test following the if or elif reserved words,
part of any command executed in a && or || list except the
com
On Fri, Dec 22, 2017 at 1:39 PM, Kevin Layer wrote:
> The bug happens to me on
> GNU bash, version 4.1.2(2)-release (x86_64-redhat-linux-gnu)
> and
> GNU bash, version 4.4.12(1)-release (x86_64-apple-darwin16.4.0)
>
> The script is attached, but the function in question is this:
>
> function debu
