Skip Menu |
 

This queue is for tickets about the POE CPAN distribution.

Report information
The Basics
Id: 91615
Status: rejected
Priority: 0/
Queue: POE

People
Owner: Nobody in particular
Requestors: MAJUSCULE [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Provide option to enable ISIG (and handling of arbitrary signals)
Download (untitled) / with headers
text/plain 270b
It would be nice to be able to catch and handle arbitrary UNIX signals, such as SIGINT. A use case example is in POE::Wheel::Readline, where ^C could be caught and start a new input line. Thanks! http://ftp.gnu.org/old-gnu/Manuals/glibc-2.2.3/html_chapter/libc_17.html
Download (untitled) / with headers
text/plain 977b
On Mon Dec 23 22:24:56 2013, MAJUSCULE wrote: Show quoted text
> It would be nice to be able to catch and handle arbitrary UNIX > signals, such as SIGINT. A use case example is in > POE::Wheel::Readline, where ^C could be caught and start a new input > line. > > Thanks! > > http://ftp.gnu.org/old-gnu/Manuals/glibc- > 2.2.3/html_chapter/libc_17.html
I'm of the impression that POE::Kernel's documented signal handling facilities can already handle SIGINT (and any other signal present in %SIG). POE::Wheel::ReadLine's default inputrc maps C-c to the interrupt function, which returns a special INTERRUPT value. It could be made to handle other signal-generating terminal input in a similar way. If this is insufficient for your needs, I'm afraid I don't understand how it's deficient. I'm marking this ticket rejected for now, since it doesn't seem to cover new ground. If you can tell me why that's wrong, please go ahead. Your reply will automatically reopen the ticket. Thank you.
I seem to have forgotten to actually flag this ticket as rejected. Doing that now.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.