Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Re^13: CPAN and readline on windows

by syphilis (Bishop)
on Mar 26, 2009 at 17:50 UTC ( #753471=note: print w/replies, xml ) Need Help??


in reply to Re^12: CPAN and readline on windows
in thread CPAN and readline on windows

I have the same - Vista 64 (Business, SP1) and AS 5.10 64-bit (build 1004). Looks like this will remain unsolved for a little longer yet :-)

Cheers,
Rob

Replies are listed 'Best First'.
Re^14: CPAN and readline on windows
by BrowserUk (Pope) on Mar 26, 2009 at 18:00 UTC

    I have Home Premium SP1 rather than Business, but that's unlikely the cause. The only other thing that comes to mind is that I have it set up with UK keyboard & codespages etc. Are you using the default US setup?


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
      According to "Regional and Language Options" I'm using "English(Australia)". Some might argue that's contradictory.

      If you have PDL installed, I'd be interested if you could verify that the arrow keys are also not working for you in the perldl shell. (It's not going to help much - beyond indicating whether we're dealing with something exclusive to the cpan shell.)

      Cheers,
      Rob
        When I use cpan with "ReadLine support enabled", perldl or perl -MTerm::ReadLine -e"$t=Term::ReadLine->nw('test'); 1 while (defined($t->readline(': ')))", none of the navigation keys work for me either. Ctrl-A does.

        I'm using ActivePerl 5.10.0, WinXP, cmd Term::ReadLine 1.03 (latest). No unix environment or shells besides cmd.exe and command.com on the system.

        perl -MCPAN -e "$CPAN::Suppress_readline=1; shell" allows me to use the cursor keys and such.

        I can unfortunately confirm that perldl is similarly afflicted. Seems the problem is with Term::Readline.

        I ran perldl.pl under the auspices of Devel::Trace. When it eventually reach the point of waiting for input (it takes a looong time to get there!), I found that it simply never receives anything from any of the extended keys--eg. navigation keys; functions keys etc.

        That tends to imply that a different ReadMode() is being used on your system relative to mine. But that's not the whole story because even in mode 0, the extended keys should be generating a null byte input, but the trace from ReadKey() shows no response to my pressing those keys at all. That (I think) implies that they are being discarded internally to the XS component of Term::ReadKey.

        But I am at a loss to explain why that would be happening on my system and not yours. The key [sic] to resolving the issue is finding out the significant difference between your system and mine...so next time your in the uk ... :)


        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://753471]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (6)
As of 2019-07-22 12:45 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    If you were the first to set foot on the Moon, what would be your epigram?






    Results (17 votes). Check out past polls.

    Notices?