Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- Ilya Zakharevich
November 3, 2010, 10:25 pm
rate this thread
How do you interpret this as a fault of Term::ReadKey? It got an
"explicit report". Why should it indicate that it did not?
P.S. Of course, sometimes it is more useful to cheat than to
"stupidly follow the specification" in the corner cases. But
one needs to have a more-or-less clear picture of possible
consequences. As the simplest example, does wrap_msg() handle
the empty list return from GetTerminalSize()?
Re: Weird interaction between chroot jail and shell-mode
I meant that Term::ReadKey explicitly reported a screen size of 0x0, not
that a screen size of 0x0 had been explicitly reported to it. Whether
that is in fact the case, or that T::RK misinterpreted some kind of
unavailability code from the underlying terminal driver, I don't know.
Yes, it does. The core bit of the relevant code in the module
my @term=eval "use Term::ReadKey; Term::ReadKey::GetTerminalSize()";
$col=$term if (!$@);
$col=76 if (!defined $col);
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — The site's Newest Thread. Posted in » Secure Shell Forum