note
Mr. Muskrat
<p>Well, I have been setting up some new servers today (mounting them in the rack, running cables, etc) and haven't have much time to look at this.</p>
<p>I did find something interesting though. [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=160328] It seems that when Perl's safe signals were introduced, it broke [mod://Term::ReadLine::Gnu].</p>
<p>Do you need to use [mod://Term::ReadLine::Gnu] or can you use [mod://Term::ReadLine::Perl] (where this still works)?</p>
<p>If you do need it to use [mod://Term::ReadLine::Gnu] then perhaps this will work for you. Beware though! It uses unsafe signals so it can cause all sorts of nasty things to happen to the Perl process. Oh and it seems to leave the terminal in an odd state when a signal forces it to bail out.</p>
<code>
#!/usr/bin/perl
use strict;
use warnings;
BEGIN {
$ENV{PERL_RL} = 'Gnu'; # or 'Perl' to force which one to use
}
use Term::ReadLine;
use Signal::Safety;
my $term = Term::ReadLine->new('Term1');
print "Readline: ", $term->ReadLine, "\n";
$term->ornaments(0);
my $attribs = $term->Attribs;
$attribs->{catch_signals} = 0;
$SIG{TERM} = sub { print "I got a TERM\n"; exit; };
$SIG{INT} = sub { print "I got a INT\n"; exit; };
# add any additional signal handlers you want
my $prompt = 'cmd> ';
my $cmd = '';
while ( defined $cmd ) {
{
local $Signal::Safety = 0; # limit the use of unsafe signals
$cmd = $term->readline($prompt);
}
chomp($cmd);
if ($cmd =~ /^help$/) {
print "Help Menu\n";
}
else {
print "Nothing\n";
}
}
</code>
1003497
1003497