Bug#599202: ksh: env. var. set prefix for a command is not working

2010-10-07 Thread Jeffrey Green
On Oct 7, 2010, at 12:54 AM, Oliver Kiddle wrote: > "Jeffrey B. Green" wrote: >> My assumption is that two forms said to be equivalent imply the results >> of the forms are identical, they can be substituted for each other. >> Otherwise, they not not equivalent, just similar. What is your >> de

Bug#599202: ksh: env. var. set prefix for a command is not working

2010-10-06 Thread Oliver Kiddle
"Jeffrey B. Green" wrote: > My assumption is that two forms said to be equivalent imply the results > of the forms are identical, they can be substituted for each other. > Otherwise, they not not equivalent, just similar. What is your > definition of equivalent? But the man page doesn't just sa

Bug#599202: ksh: env. var. set prefix for a command is not working

2010-10-06 Thread Jeffrey B. Green
On 10/06/2010 11:22 AM, Oliver Kiddle wrote: "Jeffrey B. Green" wrote: The question is then: what do users do with the explanation on the manpage? I.e. they are not equivalent since the results are not the same. But they are equivalent "as far as the above execution of cmd is concerned". When

Bug#599202: ksh: env. var. set prefix for a command is not working

2010-10-06 Thread Oliver Kiddle
"Jeffrey B. Green" wrote: > The question is then: what do users do with the explanation on the > manpage? I.e. they are not equivalent since the results are not the same. But they are equivalent "as far as the above execution of cmd is concerned". When you run XXX="hello" /bin/echo $XXX, the echo

Bug#599202: ksh: env. var. set prefix for a command is not working

2010-10-06 Thread Jeffrey B. Green
On 10/06/2010 10:03 AM, Oliver Kiddle wrote: Jeff Green wrote: % XXX="hello" /bin/echo $XXX When the shell see's this line, it expands $XXX itself first. It is not /bin/echo doing the expansion. Note that if you do the following, it will print hello. XXX="hello" printenv XXX The question

Bug#599202: ksh: env. var. set prefix for a command is not working

2010-10-06 Thread Oliver Kiddle
Jeff Green wrote: > > % XXX="hello" /bin/echo $XXX When the shell see's this line, it expands $XXX itself first. It is not /bin/echo doing the expansion. Note that if you do the following, it will print hello. XXX="hello" printenv XXX Oliver -- To UNSUBSCRIBE, email to debian-bugs-dist-requ

Bug#599202: ksh: env. var. set prefix for a command is not working

2010-10-05 Thread Jeff Green
Package: ksh Version: 93s+20080202-1 Severity: normal On a powerpc or an i386 machine, I do: % echo $XXX % XXX="hello" /bin/echo $XXX % (export XXX; XXX="hello"; /bin/echo $XXX) hello % % The manual states: The environment for any simple-command or function may be augmented by prefixing i