Re: bash handles bytes instead of chars

®om wrote: > printf was only a way to send 0xe282ac on stdin of each tool, it doesn't > matter how printf interprets the bytes. What is important is how the > tool ("cut" for example, or read -n) interprets them :) I don't have any control over the various implementations of `cut' out there. The

Re: bash handles bytes instead of chars

Chet Ramey a écrit : ®om wrote: Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='lin$ uname output: Linux rom-laptop 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:

Re: bash handles bytes instead of chars

®om wrote: > Configuration Information [Automatically generated, do not change]: > Machine: i486 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' > -DCONF_OSTYPE='lin$ > uname output: Linux rom-laptop 2.6.24-21-generic #1 SMP Mon Aug 25 > 17:32:09 UTC$

bash handles bytes instead of chars

Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='lin$ uname output: Linux rom-laptop 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC$ Machine Type: i486-pc-l