[arch-general] CTRL-C stops working in bash 4.0

[André Ramaciotti]

Try it, though. I'm Brazilian and I use some UTF-8 multibyte
characters (a small subset of it comparing with the Cyrillic alphabet,
which I presume you use) and I have no problems with files named with
UTF-8 characters.

When I first tried ZSH, I ditched it because of it, but it's been a
long time since UTF-8 characters are working out of the box.

On Tue, Jul 7, 2009 at 8:46 PM, Damjan Georgievski<gdamjan at gmail.com> wrote:
>>> Has anyone noticed that ctrl-c randomly stops working in the new bash?
>>
>> You might also consider taking this opportunity to switch to ZSH.
>
> I've just installed it, then I read this .. and it's a deal breaker:
>
> Q: Does zsh support UTF-8?
>
> A: zsh's built-in printf command supports "\u" and "\U" escapes to
> output arbitrary Unicode characters. ZLE (the Zsh Line Editor) has no
> concept of character encodings, and is confused by multi-octet
> encodings.
>
> --
> damjan
>