Re: Need nudge: how to (dynamically) discover terminal width?

Thanks for all the helpful suggestions! I got it working by lifting code from studying okol(http://www.perlmonks.org/?node_id=581144)'s The Last Menu You Need to Write. In my code it looks like

# Get max display width; either get it via 'resize' for xterms or defa
+ult to 180.
my ($w) = qx#/usr/bin/resize# =~ /(\d+)/;
$w ||= 180;
[download]

Works great ('cause it gets checked every time a histogram needs to be plotted.)

Comment on Re: Need nudge: how to (dynamically) discover terminal width? Download Code

Replies are listed 'Best First'.
Re^2: Need nudge: how to (dynamically) discover terminal width? by polypagan (Initiate) on Dec 01, 2010 at 00:17 UTC
Okay, I'm back for more. The method I outlined above works fine for Linux, or course. However it isn't transportable (to Mac OS X, in particular), since Mac OS doesn't seem to implement resize at all. I switched to the Term::ReadKey approach (which also works beautifully), which can be implemented on Mac by simply installing the module, as in Linux. I am less than satisfied with this, however. What I wrote is a script. Except for certain ping features which require superuser priv, it can be run by any user who can grok "man ping". To make it work with the module, one needs to find, download, make and install Term::ReadKey, which requires superuser access (!) Yes, I know I could just bundle ReadKey.pm and reference it in the current directory... That doesn't seem quite clean either, does it? Anyone have any other ideas? Perhaps I simply need to be satisfied as it is and move on... Again, many thanks for all your help and for this excellent resource! Daniel	[reply]

Replies are listed 'Best First'.

Re^2: Need nudge: how to (dynamically) discover terminal width?
by polypagan (Initiate) on Dec 01, 2010 at 00:17 UTC

Okay, I'm back for more. The method I outlined above works fine for Linux, or course. However it isn't transportable (to Mac OS X, in particular), since Mac OS doesn't seem to implement resize at all. I switched to the Term::ReadKey approach (which also works beautifully), which *can* be implemented on Mac by simply installing the module, as in Linux. I am less than satisfied with this, however. What I wrote is a script. Except for certain ping features which require superuser priv, it can be run by any user who can grok "man ping". To make it work with the module, one needs to find, download, make and install Term::ReadKey, which requires superuser access (!) Yes, I know I could just bundle ReadKey.pm and reference it in the current directory... That doesn't seem quite clean either, does it? Anyone have any other ideas? Perhaps I simply need to be satisfied as it is and move on... Again, many thanks for all your help and for this excellent resource! Daniel

[reply]