Subject: bin/15667: window(1) blanks last column after vi(1) invocation in an xterm
To: None <gnats-bugs@gnats.netbsd.org>
From: None <vincent@labri.fr>
List: netbsd-bugs
Date: 02/19/2002 11:49:31
>Number: 15667
>Category: bin
>Synopsis: window(1) blanks last column after vi(1) invocation in an xterm
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: bin-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Feb 19 02:50:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Aymeric Vincent
>Release: NetBSD 1.5.3_ALPHA
>Organization:
LaBRI - Université Bordeaux I
>Environment:
System: NetBSD bastide 1.5.3_ALPHA NetBSD 1.5.3_ALPHA (BASTIDE) #9: Fri Jan 18 17:11:34 CET 2002 vincent@bastide:/usr/src/sys/arch/i386/compile/BASTIDE i386
Architecture: i386
Machine: i386
>Description:
While using window(1) in an xterm, after exiting vi(1), the last column will
remain blank for the rest of the session. The characters are virtually there,
but invisible.
Example:
blahblahblah in a 5-chars wide xterm would give:
blah
lahb
ah
Notice how the second b and the third l disappeared although there is room for
them.
o I tried it with vi, but I suppose any program using curses(3) will show this
behaviour.
o -current suffers from this too.
>How-To-Repeat:
Within an xterm:
% vi
:q
% ls -l | tr '\n' " "
# Look at the output
>Fix:
Unknown.
Possible culprits from most to least likely:
o libcurses
o window itself (although window(1) works well on a wscons terminal)
o termcap entry for xterm
o xterm itself
>Release-Note:
>Audit-Trail:
>Unformatted: