Re^3: Perl Term::ReadLine::Gnu Signal Handling Difficulties

It works for me; that is to say that when I run it and press ctrl-c, it exits with "I got a INT".

We are going to need more information about the environment where you are testing this. Let's start with operating system, version of Perl, version of Term::ReadLine::Gnu and version of GNU Readline library version should be sufficient for now.

By the way, it's impolite to cross-post without saying you've cross-posted. http://stackoverflow.com/questions/13316232/perl-termreadlinegnu-signal-handling-difficulties

Comment on Re^3: Perl Term::ReadLine::Gnu Signal Handling Difficulties

Replies are listed 'Best First'.
Re^4: Perl Term::ReadLine::Gnu Signal Handling Difficulties by sgt_b2002 (Initiate) on Nov 13, 2012 at 14:35 UTC
Thanks again for the reply. I'll be sure to mention cross positing if it happens again as well. So I've tested this in two environments and in each, the ctrl-c isn't handled until I press enter. Here are the two environments. `OS: Gentoo Linux 2.6.35 x86_64 Perl: 5.12.4 Term::ReadLine::Gnu: 1.20 readline version: 6.2_p1 OS: Gentoo Linux 3.3.8 x86_64 Perl: 5.16.1 Term::ReadLine::Gnu: 1.20 readline version: 6.2_p1` [download] As an aside, I added the following line as a quick check to make sure I'm using Term::ReadLine::Gnu when testing this on different machines. `print $term->ReadLine."\n";` Again, thanks for your help with this. :)	[reply] [d/l] [select]
Re^5: Perl Term::ReadLine::Gnu Signal Handling Difficulties by Mr. Muskrat (Canon) on Nov 13, 2012 at 14:45 UTC
My apologies. Apparently I tested this on the wrong box. I was using Term::ReadLine::Stub instead of Term::ReadLine::Gnu. I'll try again in a bit and keep you updated with what I find.	[reply]