Re: terminal size

[Thomas Dickey]

On Mon, May 01, 2017 at 05:08:51PM +0200, folkert wrote:
> Hi,
> 
> I have an application which does a newterm (on a tcp socket) with
> for type a null.
> Now I can do mvprintw and refresh but not repeatingly; then all data
> gets scrambled (printed at the wrong location).
> 
> So I wonder: if ncurses thinks that the terminal is 80x24 while in
> reality it is much bigger, does it expect the terminal to do e.g. wrap
> automatically at column 81? Because that could explain my problem. And
> if that is the case; can I disable this optimalization somehow?

yes, that's correct.

offhand, you'd probably be able to disable it by a custom terminal
description which doesn't have these flags:

        am
        bw

as well as NOT calling

        nonl();

but you'd run into problems if the screen were smaller than 80x24
(either dimension)

But it would be preferable if your application could get an appropriate
screensize via the socket (before initializing curses), and do

        putenv("LINES=xxx");
        putenv("COLUMNS=xxx");

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net

signature.asc
Description: Digital signature