>Number:         756
>Category:       bin
>Synopsis:       nvi screen corruption
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jan 27 12:20:01 1995
>Originator:     Jeff Scofield   (cs.washington.edu!cedar!jeff)
>Organization:
"Cedar River Software, Inc."
>Release:        1.0
>Environment:
	Machine = i486, OS = NetBSD 1.0
	$ ex +':vers|:q'
	Version 1.34, Wed Aug 17 11:37:48 1994
	The CSRG, University of California, Berkeley.
	$ ldd /usr/bin/vi
	/usr/bin/vi:
		-lcurses.2 => /usr/lib/libcurses.so.2.1 (0x1004f000)
		-ltermlib.0 => /usr/lib/libtermlib.so.0.0 (0x1005a000)
		-lutil.3 => /usr/lib/libutil.so.3.1 (0x1005c000)
		-lc.12 => /usr/lib/libc.so.12.0 (0x1005e000)
System: NetBSD rita.cedar.wa.com 1.0 NetBSD 1.0 (RITA) #4: Thu Jan 19 16:42:40 
PST 1995 dick@rita.cedar.wa.com:/usr/src/sys/arch/i386/compile/RITA i386


>Description:
	nvi loses track of the proper screen contents after issuing a
	specific sequence of :set commands.

>How-To-Repeat:
	The following causes the failure for me every time.  Note
	that, after the first `:set all', each successive command
	must be issued while the ``Enter return to continue:''
	prompt is visible.  In other words, enter the next colon
	at that point rather than a return.

	$ vi /etc/termcap # or any large file
	:set all
	:set nokeytime
	:set all

	Note that the ``:set nokeytime'' is intentionally an improper
	vi command.  It appears that this is essential.  I don't
	see a problem if I enter a proper command (such as ``:set
	keytime=0'') at this point.

>Fix:
	Since the problem shows up only in exceedingly specific
	cases, it's easy to avoid it.

>Audit-Trail:
>Unformatted: