Re: LYNX-DEV Control-Z and SIGSTOP mysteries

[T.E.Dickey]

> Ok, I've figured out the exact problem!  I did an stty -a with both login
> methods, and diff'ed the two.  When logging in via the DECServer, rows and
> columns are both set to 0.  When I log in using a telnet program on the
> PC, rows and columns are set to 24 and 80 (or whatever size I have the
> window set to).  By manually entering 'stty rows 24 cols 80' at the prompt
> before using lynx when logged in via the DECServer.  Is this normal
> behavior?  I tried this on the Linux box (setting stty rows 0 cols 0) and
> it still suspended and resumed properly (ncurses).
it's unfriendly to have the size set to 0's, but all it means is that
the application relied on an ioctl to get the size, couldn't get it &
didn't assume 24x80 (that should be the fallback default).  Does your
connection also set the $TERM to something like 'network'?  (I usually
have some configuration like that, which needs to be mapped to vt100).
 
> Incidentally I did some tests to see if I could figured out WHAT was
> causing it not to work, and 'stty rows 24 cols 0' causes a core dump upon
> exiting lynx on HP if it has been suspended and resumed.  'stty rows 0
> cols 80' acts like both being 0.  So, the only way to get it to work
> properly is to have both set to non-zero values.
right - because it's probably testing if they're both zero as the sign
of failure.

-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;