Luke Goodsell ogt.com> writes:
> > Please report this upstream.
>
> To whom would that be? Perl devs?
The module is on CPAN, with the following link to the bug tracker:
https://rt.cpan.org/Public/Dist/Display.html?Name=TermReadKey
Regards,
Achim
--
Problem reports: http://cygwin.com/pr
Hi Achim,
> The stacktrace is useless, but if you run this under strace you'll also see a
> message that doesn't make it to the output otherwise:
That arises from the subsequent print statement, which is never reached under
cygwin.
Alternative command that eliminates that warning:
perl -MTerm
Hi Marco,
> $ perl -MTerm::ReadKey -E 'my $input = "\0" ; open(my $stdin, "<", \$input)
> or die "failed to open: $!"; local *STDIN = $stdin; ReadMode "raw"; my
> $response = ReadKey(1, \*STDIN); ReadMode "normal"; print "Got
> \"$response\"\n";'
> Got ""
I get:
> Got " "
... whereas I wou
Luke Goodsell ogt.com> writes:
> Please can you help me to diagnose this issue?
The stacktrace is useless, but if you run this under strace you'll also see
a message that doesn't make it to the output otherwise:
syntax error at -e line 1, near "= ;"
Unterminated <> operator at -e line 1.
The re
On 25/08/2015 10:48, Luke Goodsell wrote:
perl -MTerm::ReadKey -e 'my $input = ""; open(my $stdin, "<", \$input) or die "failed to open: $!"; local *STDIN =
$stdin; ReadMode "raw"; my $response = ReadKey(1, \*STDIN); ReadMode "normal"; print "Got \"$response\"\n";
I will bet in a lack of strin
Hi,
Please can you help me to diagnose this issue?
Attempting Perl Term::ReadKey from an empty string under Cygwin causes perl to
segmentation fault. The same command on Debian, or with a non-empty string,
works fine.
Example command:
> perl -MTerm::ReadKey -e 'my $input = ""; open(my $stdin,
6 matches
Mail list logo
