Your message dated Sat, 9 Sep 2006 16:52:34 -0400
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #386730,
regarding zsh: printf doesn't handle single-digit and two-digit octal escapes
to be marked as having been forwarded to the upstream software
author(s) [EMAIL PROTECTED]
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Will changing getkeystring() break anything?
> zsh's builtin printf fails to interpret two-digit octal escape, such as '\1'
> or '\33'. For example:
>
> zsh% printf '\33abc' | hd
> 00000000 5c 33 33 61 62 63 |\33abc|
> 00000006
>
> On the other hand, the printf from textutils handles them:
>
> $ /usr/bin/printf '\33abc' | hd
> 00000000 1b 61 62 63 |.abc|
> 00000004
>
> The zshbuiltins man page promises "formatting rules are the same as used in
> C", and C explicitly supports single-digit and double-digit octal escapes in
> string and character literals -- see section "6.4.4.4 Character constants"
> of the C99 standard.
>
> Furthermore, POSIX explicitly states that \d and \dd are supported by
> printf(1) -- see http://tinyurl.com/gkdfr/, extended description, item 3.
> The Solaris printf(1), the bash printf builtin, and the FreeBSD printf(1)
> all support them.
--- End Message ---
