Subject: bin/2077: window should probably set term
To: None <gnats-bugs@NetBSD.ORG>
From: Chris Jones <>
List: netbsd-bugs
Date: 02/14/1996 17:03:35
>Number:         2077
>Category:       bin
>Synopsis:       window should probably set term
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Feb 14 20:35:01 1996
>Originator:     Chris Jones
* Chris  | "You can't say that Microsoft hasn't ever put the buggy       *
*  Jones |  before the horse."                             -Mark Wistey  *
>Release:        1.1
System: NetBSD 1.1 NetBSD 1.1 (SLIM) #0: Wed Nov 22 13:02:54 MST 1995 mac68k

Window does a reasonable, but not complete, job of communicating the
terminal type to its child shells.  It sets TERMCAP, but it doesn't
set TERM.  I don't know what the "correct" behavior for a curses-style
program is, but emacs for one checks TERM before TERMCAP.  So when I
go into window, TERM is still set to vt100, even though vt100 codes
won't do things for window.  The result is that programs can't
communicate properly with window.
% window
win1% printenv TERM
I just fixed my .windowrc like this, but it seems to be something that
should be system-wide:

write(1, "set term=window-v2\n");
write(2, "set term=window-v2\n");