Am Dienstag, 8. März 2005 08:29 schrieb Dan Nelson: > In the last episode (Mar 08), Emanuel Strobl said: > > When I open a xterm on the local machine, say with 100x37, vi and man > > recognizes the size and display the content correctly. If I use > > cu/tip in a 100x37 xterm "ls" works fine (uses all lines) as long as > > I start vi but man doesn't work (no scrolling possible). After the vi > > session only 24 lines (or whatever type I set in /etc/ttys) are used, > > but man works correctly. Why can I use different terminal sizes on > > the local machine and in ssh sessions but not over a serial console? > > If I set "setenv LINES 37" and "setenv COLUMNS 100" it works also on > > the serial line but why or how can vi and others know what size my > > terminal is via ssh session? I'm sure this behaviour is adoptable to > > serial consoles too. > > Telnet and ssh have out-of-band control sequences that let the client > pass things like terminal size to the server. There's no equivalent
Where are they set? I can't find any environment variable which reflect this. > for serial lines. You can get the screen size from vt100 terminals > (and many emulators) though, by moving the cursor to the far > lower-right corner, asking the terminal for the cursor position, and > reading the result on stdin. Even with knwon values I have the problem that when I recall the previous command in tcsh which was longer than one line there's no linefeed, the second line overwrites the first line. My problem is that I don't really understand how and why different applications seem to use different methods of displaying text and determining size values. man, vi and tcsh are at least very different. Any links highly appreciated. Thanks a lot, -Harry
pgpcLTdmtjPde.pgp
Description: PGP signature
