Skip Menu |

This queue is for tickets about the POE CPAN distribution.

Report information
The Basics
Id: 4825
Status: resolved
Priority: 0/
Queue: POE

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

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



Subject: augment Term::Cap use in Wheel::ReadLine
Term::Cap often reports keystrokes (for example, the arrow keys) that have nothing to do with what a keyboard generates. The blame for this behavior has not yet been squarely set. However, we have determined this: 1. Term::Cap returns the correct information, based on /etc/termcap and the current TERM environment variable. 2. The keyboard generates whatever it damn well pleases, despite a properly configured TERM and /etc/termcap. 3. Term::ReadLine works. It works because it ignores Term::Cap and hardcodes the keystroke strings in Term::ReadLine::readline. Therefore, we should honor Term::Cap but also include common keystroke encodings to cover our butts. It seems Term::ReadLine hardcodes them to cover its butt, and it looks like it's had the same bad experiences we're going through with Term::Cap. -- Rocco Caputo - rcaputo@pobox.com - http://poe.perl.org/