> 1. how can window resizing information be passed on to the running perl process (such as sigwinch) then

assign a coderef to $SIG{WINCH}

> 2. how do I resize my output parameters to match.

Without knowing your code, I'd say try to access the settings in the callback

see also To find out console line size in char.s .

you may also want to give Curses a try.

G'day jason0,

You provide very little in the way of details, which means that only a very generalised solution can be provided.

Here's some suggestions based on the assumption that you have code something like:

open my $cmd_pipe, '-|', 'iostat -w1';
[download]

And that you're reading from $cmd_pipe line-by-line which, in turn, forms the basis for what you output to the screen (and without any knowledge of what the header line(s) look like).

• You could use Term::Size::Any (or similar) to get the current terminal size. Then, based on a count of the lines already output and the number of lines needed for the header, conditionally output a new header.
• Take a look at "perlipc: Signals" for information on signal handling.
• Some sort of GUI front-end (e.g. Tk) might be an alternative to consider.

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.

I would write your getRowsCols-sub like this:

sub getRowsCols {
  qx|/bin/stty size| =~ /(\d+)\s+(\d+)/;
}
[download]

Is there anything gained in your (more complicated imho) way?

> Is there anything gained in your (more complicated imho) way?

Well he has 2 points of error handling.

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!}