Re: Bash and Unicode

2012-09-21 Thread Andreas Schwab
Your keyboard input apparently uses UTF-8 encoding, so the single character ó is represented by two bytes with the values 195 and 179. This has nothing at all to do with the shell, most likely your locale settings are messed up. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerpri

Re: Bash and Unicode

2012-09-21 Thread Jakub Jankiewicz
On Fri, 21 Sep 2012 09:11:45 +0200 Andreas Schwab wrote: > Your keyboard input apparently uses UTF-8 encoding, so the single > character ó is represented by two bytes with the values 195 and 179. > This has nothing at all to do with the shell, most likely your locale > settings are messed up. >

Re: Bash and Unicode

2012-09-21 Thread Andreas Schwab
Jakub Jankiewicz writes: > In locale I have pl_PL.UTF-8 which I didn't change and everything work > except bash. Then it's a bug in python if it cannot properly parse its command line. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5

Re: Bash and Unicode

2012-09-21 Thread Andreas Schwab
Did you read ? Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."

Re: Bash and Unicode

2012-09-21 Thread Jakub Jankiewicz
On Fri, 21 Sep 2012 11:46:26 +0200 Andreas Schwab wrote: > Did you read ? > > Andreas. > I forget about it, this work: python -c '# coding: utf-8 print ord(u"ó")' Probably interactive python have enabled it by default. I try to test sed if I can sw

Re: Bash dumps stack after writing to /etc

2012-09-21 Thread Eric Blake
On 09/21/2012 06:24 AM, Axel Svensson wrote: > Machine: i686 > OS: cygwin on Windows 7 Professional SP1 > Compiler: gcc-4 > Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' > -DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i686-pc-cygwin' -DCONF_VENDOR='pc' > -DLOCALEDIR='/usr/$ > uname out