Paul Jarc wrote:
>> | The function is named fname; the application shall ensure that it is a
>> | name (see the Base Definitions volume of IEEE Std 1003.1-2001, Section
>> | 3.230, Name).
>
> "The application" is the script, not the shell, so this is consistent
> with Stephane's statement.
Ok, g
Jan Schampera <[EMAIL PROTECTED]> wrote:
> Stephane Chazelas wrote:
>> Note that bash didn't have to. POSIX allows a shell to accept
>> any character in a function name, but it says one shouldn't use
>> those in a POSIX script, which is different.
>
> I'm not a POSIX expert, and this is the SUS, bu
Stephane Chazelas wrote:
> Note that bash didn't have to. POSIX allows a shell to accept
> any character in a function name, but it says one shouldn't use
> those in a POSIX script, which is different.
I'm not a POSIX expert, and this is the SUS, but I read:
| The format of a function definitio
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
The man page says that bash builtin printf supports the standard printf(1)
formats. But it seems that \u is not working:
$ /usr/bin/printf '\u212b\n'
Å
$ printf '\u212b\n'
\u212b
Am I doing something wrong here?
I see the same behavior with
GNU bash, version 3.2.13(1)-release (i486-pc-linux-
