Alan Hourihane wrote:
> On Fri, 2009-05-15 at 13:19 +0200, Roman Rakus wrote:
>> On 05/15/2009 12:02 PM, Alan Hourihane wrote:
>>> Hi all,
>>>
>>> I've just compiled bash 4.0 p17 and noticed that CTRL+C isn't having any
>>> effect until I hit.
>>>
>>> bash 3.2 worked perfectly, so I'm a little unsu
On Fri, 2009-05-15 at 13:19 +0200, Roman Rakus wrote:
> On 05/15/2009 12:02 PM, Alan Hourihane wrote:
> > Hi all,
> >
> > I've just compiled bash 4.0 p17 and noticed that CTRL+C isn't having any
> > effect until I hit.
> >
> > bash 3.2 worked perfectly, so I'm a little unsure what's caused this.
>
On 05/15/2009 12:02 PM, Alan Hourihane wrote:
Hi all,
I've just compiled bash 4.0 p17 and noticed that CTRL+C isn't having any
effect until I hit.
bash 3.2 worked perfectly, so I'm a little unsure what's caused this.
Can anyone point me at the code which handles this and I can take a
closer lo
Hi all,
I've just compiled bash 4.0 p17 and noticed that CTRL+C isn't having any
effect until I hit .
bash 3.2 worked perfectly, so I'm a little unsure what's caused this.
Can anyone point me at the code which handles this and I can take a
closer look ?
Thanks,
Alan.