|
|
Re: POE::Wheel::ReadLine: msg#00009
|
Subject: |
Re: POE::Wheel::ReadLine |
Rob Bloodgood wrote:
lanas wrote:
Hi,
When I use the POE::Wheel::ReadLine in the Cookbook I get, under SuSE 9.3,
the following errors before the prompt is shown:
ignoring "\e[5~", since function 'history-search-backward' is not known
ignoring "\e[6~", since function 'history-search-forward' is not known
ignoring "\e[5;2~", since function 'history-search-backward' is not known
ignoring "\e[6;2~", since function 'history-search-forward' is not known
ignoring "\e[5;5~", since function 'history-search-backward' is not known
(so on so forth - a few more in the same vein)
After the promt is shown, the behaviour is as it should be, no problem.
What could be the problem ? Are these 'history-search-*' functions no longer
supported in bash ? I didn't see any options in POE::Wheel::ReadLine
documentation to toggle the use of these functions.
These are settings from /etc/inputrc, to map keystrokes at the terminal.
The Wheel::ReadLine module parses this file to catch any local settings
after establishing defaults. You can probably safely comment those
lines out in /etc/inputrc, unless you're actually using those keystrokes.
L8r,
Rob
Indeed, rob is correct. In POE, the actual function name is
'forward-search-history' and not 'history-search-forward'. This looks
like the author of POE::Wheel::ReadLine was being particulary dyslexic
at the time. I'll have words with him and get a patch submitted :).
Furthermore, it probably shouldnt' dump error lines to the output stream
like that as it's particularly unfriendly.
Nick
|
| |