this is behaviour changed upstream:
"Changed from 3.1 to 3.2, for Posix
conformance. `echo -e' (and the corresponding xpg_echo shell option)
now conform to the POSIX standard and accept 0-3 octal digits after a
(required) leading `\0'.
The xpg_echo and `echo -e' code should be identical. T
** Changed in: bash (Ubuntu)
Importance: Undecided => Medium
--
echo does not handle escapes any more
https://bugs.launchpad.net/bugs/116226
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Was able to reproduce in Gutsy and Feisty
** Changed in: bash (Ubuntu)
Status: New => Confirmed
--
echo does not handle escapes any more
https://bugs.launchpad.net/bugs/116226
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Tested this in Feisty and problem exists.
I thought it amusing that when trying to look at the versions I got
this:
:~$ /bin/echo --version
echo (GNU coreutils) 5.97
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software. You may redistribute copies of it under the terms of
the
echo '\0101' works, but it should IMHO still keep the old behaviour too
to not break compatibility with existing scripts.
--
echo does not handle escapes any more
https://bugs.launchpad.net/bugs/116226
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
