clone 477969 -1
reassign -1 bash
found -1 3.2-2
notfound -1 3.1dfsg-9
retitle -1 bash: echo -e no longer interprets \nnn
thanks
On 27/04/08 at 23:00 +0200, Ola Lundqvist wrote:
> Hi Lucas
>
> Thanks for the report.
>
> However I do not understand the error code in this case. It complains about
> a stray '\' but there is no '\' character in that file. Have you seen this
> before and know what the problem is?
drivers.c contains:
static const CALDRIVER *driver_registry\133\135 = {
&icap_driver,
&mstore_driver,
NULL
};
note the \133\135, which isn't there after unpacking the sources.
It seems to be that configure is at fault here:
rm --force drivers.c
echo -e 'static const CALDRIVER *driver_registry\133\135 = {' > drivers.c
This is caused by a change in bash 3.2. With bash 3.1:
*** [EMAIL PROTECTED]:~$ printf '\133\n'
[
*** [EMAIL PROTECTED]:~$ echo -e '\133'
[
With bash 3.2:
grelon-62:~# printf '\133\n'
[
grelon-62:~# echo -e '\133'
\133
This seems to be on purpose (the man page was updated as well), but I'm not
sure if it's correct.
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
