No, it isn't the behavior we have seen. It NEVER executes the external command! If it finds an external command before it gets to /bin in $PATH, it executes the internal echo in "att mode" otherwise it uses "ucb mode".
If it _were_ executing the local command, there would be NO difference in behavior, because the external echo command does not expand backslash escapes by default. Kevin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of inode0 Sent: Friday, July 06, 2007 1:58 PM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: Re: [rhelv5-list] how to handle "echo" ? On 7/6/07, Collins, Kevin [MindWorks] <[EMAIL PROTECTED]> wrote: > Well, I have now found an official description of the expected behavior. > >From src/cmd/ksh93/COMPATIBILITY: > > > 10. Built-ins in ksh-88 were always executed before looking for > the command in the PATH variable. This is no longer true. > Thus, with ksh-93, if you have the current directory first > in your PATH, and you have a program named test in your > directory, it will be executed when you type test; the > built-in version will be run at the point /bin is found > in your PATH. > > However, now I am MORE confused because this is telling me that it > _should_ execute the external command. Wait, this makes sense. It looks for the external one in your PATH until it hits /bin at which point it uses the built-in. That is exactly the behavior we have seen. Changing the UNIVERSE changes the behavior of the built-in echo unless I'm all confused at this point which is certainly possible. :) John _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
