Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!www.nntp.primenet.com!nntp.primenet.com!dispatch.news.demon.net!demon!awfulhak.demon.co.uk!awfulhak.demon.co.uk!awfulhak.demon.co.uk!not-for-mail
From: brian@anorak.coverform.lan (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: VI slow start-up
Date: 10 Nov 1996 04:21:19 -0000
Organization: Coverform Ltd.
Lines: 38
Sender: brian@awfulhak.demon.co.uk
Message-ID: <563l7v$14a@anorak.coverform.lan>
References: <55nlkf$ecr@news.ox.ac.uk> <328272C4.4758@indy.celebration.net>
<55v3l2$phq@news.ox.ac.uk>
Reply-To: brian%anorak.coverform.lan@awfulhak.demon.co.uk
NNTP-Posting-Host: localhost.coverform.lan
X-NNTP-Posting-Host: awfulhak.demon.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
In article <55v3l2$phq@news.ox.ac.uk>,
Neil Long <neil.long@materials.oxford.ac.uk> writes:
: "John S. Dyson" <dyson@indy.celebration.net> writes:
:
>>Neil Long wrote:
>>>
>>> Just curious (again). Is there any reason why vi should start-up so
>>> slowly when run on the PC console compared to a remote login?
>>>
>>> I find it takes 10-12 seconds on the PC consoles and only a couple of secs
>>> if I rlogin from elsewhere. (no filename and irritatingly reproducible)
>>>
>>> I am running 2.2-961014-SNAP on a 486/33 with 20M, plenty of swap unused.
>>>
>>Just a guess -- move your console's termcap entry to near the beginning
>>of the file?
:
>>John
:
: Yes moving cons25 to the top improves it a lot but it still takes 4 secs-ish
: compared with 2-ish via an xterm/vt100 network connection.
:
: The developers must never use the consoles I guess!
Have you got a good /usr/share/misc/termcap.db (man cap_mkdb) ?
I had such problems with 960323-SNAP - and found it mildly irritating. I
recently upgraded to 961014 and also put it on our development machine at
work, and the problem went away.... I didn't know about termcap.db then.
Bear in mind, you can also set your TERMCAP variable to the termcap entry
itself. If all else fails, this will make things *very* quick.
--
Brian <brian%anorak.coverform.lan@awfulhak.demon.co.uk>
<http://www.awfulhak.demon.co.uk/>
Don't _EVER_ lose your sense of humour....
.