[Miquel van Smoorenburg] Re: Bug#203693: due to sourcing, nobody can tell what file the problem occurred in

[Dan Jacobson]

Dear bash bug: Miquel van Smoorenburg <miquels@cistron.nl> says:

That's a bug in bash. Ash actually gets this right.

Test script:

#! /bin/sh
# script 1

echo Executing script2
. script2
echo Done, back at script 1

#! /bin/sh
# script 2#
/not/there

$ bash script1
Executing script2
script1: line 3: /not/there: No such file or directory
Done, back at script 1

$ ash script1
Executing script2
script2: 3: /not/there: not found
Done, back at script 1

See? This is a bug in bash. I should probably just reassign
it to bash.