> -Original Message-
> From: David T-G [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 04, 2002 2:51 PM
> To: perl beginners
> Cc: Bob Showalter
> Subject: Re: printing key codes
>
> ...
>
> %
> % Then you can just refer to F1 as K_F1, etc.
&g
Bob, et al --
...and then Bob Showalter said...
%
% > -Original Message-
% > From: David T-G [mailto:[EMAIL PROTECTED]]
...
% >
% > Is there a simple way to get perl to spit out one line per incoming
% > keycode? That is, get it to spit out
% >
% > 27, 79, 80
% > 27, 91, 50, 51, 1
> -Original Message-
> From: David T-G [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 04, 2002 1:04 PM
> To: perl beginners
> Cc: Bob Showalter
> Subject: Re: printing key codes
>
>
> Bob, et al --
>
> ...and then Bob Showalter said...
> %
> %
Jeff --
...and then Jeff 'japhy' Pinyan said...
%
% On Jun 4, David T-G said:
%
% >%perl -lpe '$_ = join ", ", unpack("c*", $_)'
% >
% >Is there a simple way to get perl to spit out one line per incoming
...
% >when it sees F1 followed by Shf-F1 without a newline between them?
%
% You run
On Jun 4, David T-G said:
>Bob, et al --
>%
>%perl -lpe '$_ = join ", ", unpack("c*", $_)'
>
>Is there a simple way to get perl to spit out one line per incoming
>keycode? That is, get it to spit out
>
> 27, 79, 80
> 27, 91, 50, 51, 126
>
>when it sees F1 followed by Shf-F1 without a newl
Bob, et al --
...and then Bob Showalter said...
%
% > -Original Message-
% > From: David T-G [mailto:[EMAIL PROTECTED]]
...
% > which will read stdin, spit out the key codes it gets until a
...
%
% How 'bout:
%
%perl -lpe '$_ = join ", ", unpack("c*", $_)'
Aha! So I need to go a
> -Original Message-
> From: David T-G [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 04, 2002 12:48 PM
> To: perl beginners
> Subject: printing key codes
>
>
> Hi, all --
>
> It seems like it should be a very easy thing to whip up a
> perl one-liner
> which will read stdin, spit out
