CTRL-C stops working in bash 4.0

[Damjan Georgievski]

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.

If I start python in the same terminal, it will notice the ctrl-c, so
it's not the terminals fault.

This started to happen with bash 4.0


--
damjan

[Daenyth Blank]

On Mon, Jul 6, 2009 at 18:46, Damjan Georgievski<gdamjan@...> wrote:
> Has anyone noticed that ctrl-c randomly stops working in the new bash?

I haven't noticed this (plain urxvt)

[Henning Garus]

On Tue, Jul 7, 2009 at 12:46 AM, Damjan Georgievski<gdamjan@...> wrote:
> 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?

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

[Dieter Plaetinck]

On Tue, 7 Jul 2009 01:19:41 +0200
Henning Garus <henning.garus@...> wrote:

> On Tue, Jul 7, 2009 at 12:46 AM, Damjan
> Georgievski<gdamjan@...> wrote:
> > 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?
>
> [1] http://lists.schmorp.de/pipermail/rxvt-unicode/2009q2/000923.html
> [2]
> http://groups.google.com/group/gnu.bash.bug/browse_thread/thread/f1729727b17a6dd6/8fb77fe31705fabb

I have this problem for already a month or two. eg
before bash 4.0
Also using urxvt (and wmii). I'v just been too lazy to seek help.
So I'll just wait for fixed packages I guess :)

Dieter

[Damjan Georgievski]

>> 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/f1729727b17a6dd6/8fb77fe31705fabb
>



--
damjan

[Tuong Nguyen Manh]

Damjan Georgievski wrote:
> 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.
>
> If I start python in the same terminal, it will notice the ctrl-c, so
> it's not the terminals fault.
>
> This started to happen with bash 4.0
As a workaround you could start urxvt with the command to start bash and
exit again:

urxvt -e sh -c 'bash;exit'

At least, this works for me using xmonad.

[Cedric Staniewski]

Damjan Georgievski wrote:

> 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.
>
> If I start python in the same terminal, it will notice the ctrl-c, so
> it's not the terminals fault.
>
> This started to happen with bash 4.0
>
>

You should give the patch from [1] a try. It fixes ctrl-c for me.

[1] http://bbs.archlinux.org/viewtopic.php?id=75478

[Andrei Thorp]

Excerpts from Damjan Georgievski's message of Mon Jul 06 18:46:08 -0400 2009:
> Has anyone noticed that ctrl-c randomly stops working in the new bash?

You might also consider taking this opportunity to switch to ZSH.
--
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)

[Damjan Georgievski]

>> 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

[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@...> 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
>

[Christoph Schied]

On Tue, Jul 07, 2009 at 09:16:11AM -0400, Andrei Thorp wrote:
> You might also consider taking this opportunity to switch to ZSH.

zsh has Problems with this urxvt behaviour too.

[Andrei Thorp]

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<gdamjan@...> 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)