...

Has anyone noticed that ctrl-c randomly stops working in the new bash? I use rxvt-unicode 9.06-2 and it happens in a terminal where ctrl-c worked while typing bash commands, it will suddenly stop working ie bash will not recognise the key-press.

There was a bug which stopped ctrl-c from working prior to bash 4.0.020 which appeared in conjunction with urxvt and tiling WMs, there is a thread on the urxvt ML [1] and on gnu.bash.bug [2]. This should be fixed by now. Are you using the newest bash package?

bash 4.0.024-1 and awesome 3.3-2

[1] http://lists.schmorp.de/pipermail/rxvt-unicode/2009q2/000923.html [2] http://groups.google.com/group/gnu.bash.bug/browse_thread/thread/f1729727b17...

-- damjan

...

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

Excerpts from André Ramaciotti's message of Tue Jul 07 19:58:10 -0400 2009:

On Tue, Jul 7, 2009 at 8:46 PM, Damjan Georgievski 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. 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.

Beat down and then redeemed :D -- Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)