Good question, but I have been installing -current from scratch each time.
I've made few enough changes for me that I've just kept modified files on my
Windows partition and copy them over after installation.
Just to be perfectly clear here, when I go into vi all lower case characters
are changed to graphics characters. I have to get the escape sequences
that the "unflash" program uses to reset myself. From what I read on this
list before, that WAS the problem that others were seeing--right?
This is using a ThinkPad 1480i, with -current of 3/28.
--STeve Andre'
At 11:00 AM 3/29/00 -0600, Adam Thompson, MCNE, MCSE wrote:
Dumb question here, but have you rebuilt your termlib tree from
/usr/src? Nothing actually uses termlib.master except the build/install
process, so if you have old compiled files hanging around, they'll
interfere.
You may want to do (I know, I know...):
find / -name vt220 -print
just to be on the safe side... I'm not sure about OpenBSD's, but many
curses libs will search multiple paths for termlib entries.
Also, make sure you're using a regenerated copy of /etc/termcap.
STeve Andre' wrote:
> Using -current of 3/28, I find that I still have to set the TERM
type to
> vt220-old in order to use vi and friends. ...I thought that had been fixed
> in an earlier version of -current?
--
Adam Thompson, MCNE, MCSE, CWT, A+
Vice-President / Chief Technology Officer, Commerce Design Inc.
<athompso@commerced.com>
tel: (204) 942-1648, fax: (204) 989-8080, cell: (204) 782-6198
|