Date: Tue, 8 Mar 2005 01:29:19 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Emanuel Strobl <emanuel.strobl@gmx.net> Cc: freebsd-questions@freebsd.org Subject: Re: ttydX and xterm size (LINES and COLUMNS understanding) Message-ID: <20050308072919.GD37452@dan.emsphone.com> In-Reply-To: <200503080734.46757@harrymail> References: <200503080734.46757@harrymail>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050308072919.GD37452>