Here's a little test program I built a while back to try this out. Run it in a terminal window such xterm and it will report the terminal size as you change it.

use strict;
use warnings;

use feature qw{ say };

$SIG{ WINCH } = \ &winch;

winch();

while ( 1 )
{
    sleep 200;
}

sub winch
{
    my( $rows, $cols ) = getRowsCols();
    say qq{Rows = $rows - Columns = $cols};
}

sub getRowsCols
{
    my $sttyOut = do {
       open my $sttyFH, q{-|}, qw{ /bin/stty size }
          or die qq{fork: /bin/stty size: $!\n};
       local $/;
       <$sttyFH>;
       };
    die qq{/bin/stty size: Unexpected output:  $sttyOut}
       unless $sttyOut =~ m{^(\d+)\s+(\d+)$};
    return $1, $2;
}

[download]

I hope this is helpful.

Cheers,

JohnGG

In reply to Re: handling terminal window resizing by johngg
in thread handling terminal window resizing by jason0

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.