Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!yarrina.connect.com.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!math.ohio-state.edu!jussieu.fr!univ-lyon1.fr!swidir.switch.ch!scsing.switch.ch!news.dfn.de!zeus.rbi.informatik.uni-frankfurt.de!terra.wiwi.uni-frankfurt.de!news.th-darmstadt.de!odb!incom!kauss.rhein-main.de!kauss.rhein-main.de!not-for-mail From: ska@kauss.rhein-main.de (Stephan Kauss) Newsgroups: comp.os.386bsd.bugs Subject: re: FreeBSD2.0R: Fix Problem with vi in a xterm Date: 7 Jan 1995 20:14:46 +0100 Organization: Stephan Kauss Lines: 27 Message-ID: <3emp76$or@kauss.rhein-main.de> NNTP-Posting-Host: kauss.rhein-main.de X-Newsreader: TIN [version 1.2 PL2] Hi Folk's day's befor I wrote this message : >Hi Folk's, > >I have problems with the "vi" in my xterm. >The "vi" use only 23 lines (My xterm has 38 lines). So if I edit a file >I type the ^l very offten. >The command "resize" didn't change the problem. I set the TERM and TERMCAP >variable correct. > >May be the "vi" didn't use the TERMCAP variable. Now I find the problem : I set in my .login the enviroment variable "LINES" and "COLUMNS". I do a view in the "vi" sources and do a debug in the file sex_window.c. Here they get the correct row and columns information and on the end of the function there are some queasy line's for the POSIX 1003.2 compatibility and override the correct information. So my tip is don't set the enviroment LINES and COLUMNS ! Stephan