bin/42836: window(1) display error on most TERMs

[cberardi%natoufa.com@localhost]

>Number:         42836
>Category:       bin
>Synopsis:       window(1) display error on most TERMs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Feb 17 13:50:00 +0000 2010
>Originator:     Christopher Berardi
>Release:        5.0.2
>Organization:
>Environment:
NetBSD natoufa.dnsalias.net 5.0.2 NetBSD 5.0.2 (GENERIC) #0: Sat Feb  6 
17:53:27 UTC 2010 
builds%b7.netbsd.org@localhost:/home/builds/ab/netbsd-5-0-2-RELEASE/i386/201002061851Z-obj/home/builds/ab/netbsd-5-0-2-RELEASE/src/sys/arch/i386/compile/GENERIC
 i386

>Description:
When using window(1), the only TERM that displays properly is window-v2. Every 
other TERM I've tried (vt100, vt220, wsvt25, xterm, linux) all have display 
errors. When running a program such as top, vi, mutt, mc, etc. the display is 
quickly overwhelmed by gobbledygook (TERMCAP entries?) which makes the program 
completely unusable. I've experienced this problem both on 5.0.1 and on the 
current 5.0.2 (I don't know if this was a problem on earlier releases).

For me, since I define TERM in my shrc, it is automatically exported when I 
start window(1). Switching to TERM=window-v2 works around this, but that TERM 
appears to lack several key features I need (like ISO 8859-1 extended 
characters). 
>How-To-Repeat:
Start window(1) and switch to a non-window-v2 TERM (say vt220). Then start a 
program such as top or vi. You can switch back to window-v2 and all is well 
again.
>Fix: