On Thursday 18 September 2008 16:16, Marc W. Abel wrote:
> Hi,
>
> Apologies if this has gone through this list in prior months/years; I
> would have to download all to check!
>
> I propose this change to libbb/process_escape_sequence.c
>
> FROM
> static const char charmap[] ALIGN1 = {
> 'a', 'b', 'f', 'n', 'r', 't', 'v', '\\', 0,
> '\a', '\b', '\f', '\n', '\r', '\t', '\v', '\\', '\\' };
>
> TO
> static const char charmap[] ALIGN1 = {
> 'a', 'b', 'e', 'f', 'n', 'r', 't', 'v', '\\', 0,
> '\a', '\b', 27, '\f', '\n', '\r', '\t', '\v', '\\', '\\' };
>
> for the purpose of supporting the \e escape sequence for the ASCII
> escape character. This sequence has long been recognized by GNU gcc and
> GNU bash.
Please give an example where busybox's behavior differs from
corresponding "standard" tool.
> In the translate-to (last) line of the change, I suggest using 27 in
> lieu of '\e' in case someone builds BusyBox with a compiler which does
> not support '\e'.
Makes sense.
--
vda
_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox
