What you are probably missing is that the "extended keys" generate multiple values for each keypress.

Below shows the output when four arrow keys are pressed in the order: left, right, up, down:

use Term::ReadKey;;
{ 
    ReadMode(4); 
    print ord($c), " : '$c'" while ($c=ReadKey(0)) ne "\cM"; 
    ReadMode(0) 
};;
27  : '←'
91  : '['
68  : 'D'
27  : '←'
91  : '['
67  : 'C'
27  : '←'
91  : '['
65  : 'A'
27  : '←'
91  : '['
66  : 'B'
[download]

So, in order to match the left arrow key, you would need to use "\e[D" in your regex. But, ReadKey() returns those 3 characters one at a time, so you would need to accumulate them before you could match that.

But then the problem becomes how do you decide when you see the escape character (←, '←', "\e"; 27), whether the user has pressed the escape key, or some other keys that also generates more characters.

So there's no way to use \x52 or whatever the hex code is for the arrow keys?

So there's no way to use \x52 or whatever the hex code is for the arrow keys?

Not that I'm aware of.

---

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.

Character 0x52 is uppercase letter "R".

[ Please place blocks of computer text (e.g. code, data and output) in <c>...</c> tags. ]

The first step would be to find out what ReadKey is returning. You could use

use Data::Dumper;
{
   local $Data::Dumper::Useqq = 1;
   print(STDERR Dumper($input));
}
[download]

The left arrow key is returning "\e[D\n", and the right arrow key is returning "\e[C\n". How do I match this?

if ($input eq "\e[D\n")
[download]

and

if ($input eq "\e[C\n")
[download]

You obviously removed the lc to get those values. Be careful about re-adding lc. Only lowercase $input after checking for these special keys.

I tried implementing it within my code instead of in its own script and it returns $VAR1 = undef;. EDIT: I accidentally put it above ReadMode(0); and that's why it returned undef. Now I put it below the $input string and it returns
RIGHT ARROW

$VAR1 = "\e";
$VAR1 = "[";
$VAR1 = "c";
[download]

LEFT ARROW

$VAR1 = "\e";
$VAR1 = "[";
$VAR1 = "d";
[download]

So only one of the three characters is returned at a time. BrowserUK has already posted how to handle that.

I would suggest you check to make sure that the codes you are getting correspond to what you expect, perhaps with some code similar to

use strict;
use warnings;
use Term::ReadKey;

ReadMode(4);
my %keys = GetControlChars;
my $int = $keys{INTERRUPT};
while ((my $input = ReadKey(0)) ne $int) {
    print ord($input), "\n";
}
print ord($input), "\n";
ReadMode(0);
[download]

I would also suggest you likely want to use equality (as I've done above, see perlop) instead of regular expressions (perlre). As well, see Term::ReadKey, which does not contain a Readmode method (Perl is case sensitive).

This spits out 27 91 68 for left, and 27 91 67 for right. Now what?

This should look suspiciously similar to what BrowserUK has shown in Re: Regex arrow key problem. If you intend to capture left and right arrows, you need to handle multi-character inputs, as BrowserUK has in Re^5: Regex arrow key problem. It might be worth asking if this is an XY Problem - what is your end goal?

Edit; don't create a second node when you screw up the first.

Please state your problem clearly -- in this case, you might have asked (naively) "what values are returned by the arrow keys?" But if that's your intent, that's not a Perl question; it's one you might better answer for yourself by using Google or the like. And since you don't tell us the values to which you applied \x and \0, nor precisely how, any reply is likely to be no better than a WAG.

I hope (but am not certain) that this hint may be helpful: "keycodes" and/or "scancodes"

I clicked "update" on this post, and it created a new one for some reason. I've tried google already, and have yet to find anything that works. I've looked at scancodes and tried many different codes that I've found, all to no avail.