Re: Weird interaction between chroot jail and shell-mode

[Ilya Zakharevich <nospam-abuse@ilyaz.org>]

On 2010-11-01, Sean McAfee <eefacm@gmail.com> wrote:

> the hanging was occuring in a call to a function called "wrap_msg."
> Ultimately this routine uses the terminal size reported by the
> GetTerminalSize function in the standard Term::ReadKey module, which in
> a shell-mode shell explicitly reports a screen width and height of zero.
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> Ultimately, this would seem to be Term::ReadKey's fault.  It advertises
> a way to indicate that the terminal size could not be
> determined--returning an empty list--but instead it returns nonsensical
> screen dimensions of 0x0.

How do you interpret this as a fault of Term::ReadKey?  It got an
"explicit report".  Why should it indicate that it did not?

Yours,
Ilya

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()?