Home > Archive > PERL POE > January 2006 > POE::Wheel::ReadLine
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
POE::Wheel::ReadLine
|
|
|
| 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.
| |
| Steven Mackenzie 2006-01-12, 7:12 pm |
| It's a long time since I've used Emacs, but those lines look a lot like
you still are!
Try again in a normal shell ...
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.
>
>
>
>
>
| |
| Rob Bloodgood 2006-01-12, 7:12 pm |
| 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
| |
| Nick Williams 2006-01-13, 4:02 am |
| Rob Bloodgood wrote:
>lanas wrote:
>
>
>
>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
| |
|
| On the Thu, 12 Jan 2006 14:04:05 -0800 Steven Mackenzie has written:
> It's a long time since I've used Emacs, but those lines look a lot
> like you still are! Try again in a normal shell ...
Well I'm using emacs and that's output from the normal Konsole for SuSE
9.3. So unless emacs is like a virus and infects other
applications... ,-)
| |
|
| On the Thu, 12 Jan 2006 14:57:34 -0800 Rob Bloodgood has written:
>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.
I did that and no longer these annoying lines are there. Thanks.
| |
|
| On the Fri, 13 Jan 2006 01:57:21 -0800 Nick Williams has written:
> 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.
This would be useful when distributing the application to users who do
nto car/know how to modify their /etc7inputrc file. On the
other hand the make install for this application could add
parsing of the file, and ... ;-)
|
|
|
|
|