> On 03/04/2012 08:16 AM, Stefano Lattarini wrote:
>> What's going on there?
> That is a bug in older ksh implementations.
> I've pushed the following doc patch to describe it.
> I don't fully understand your test case, but renaming
> "script" to "script2" won't work if there happens to
> be a command named "script2" in the path, so I suggest
> changing the file name back to "script" but invoking
> it as "./script",
The fact that the script is invoked as "sh script" is deliberate, and is done
to give better coverage to the re-execution code (invocations as ./script and
/bas/path/to/script are tested separately, see the m4sh.at fragment for details).
Maybe we could rename the script to something more namespace-safe, like
"ac--script"? But honestly, I think we should cross that bridge when we come to
it (if ever).