According to alarm one / airfax security on 1/23/2010 5:49 PM: > echo does not recognize -e, and since it defaults to -E, it will not > recognize the \ items (like \n, \v etc) instead it uses \ as an escape char.
Not a bug. POSIX itself states that use of \ with echo results in non-portable behavior, because not all implementations understand -e, and among those that do, not all obey the POSIX rule that -e should be the implied default. Changing behavior (in either direction) would break existing scripts. Use printf instead. Also, before reporting echo behavior issues, be sure to distinguish whether you are using coreutils' echo (as in /bin/echo), or the shell's builtin echo. -- Don't work too hard, make some time for fun as well! Eric Blake [email protected]
signature.asc
Description: OpenPGP digital signature
