Xref: utzoo comp.unix.questions:12973 comp.bugs.misc:218
Path: utzoo!dptcdc!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!mcvax!unido!sbsvax!greim
From: greim@sbsvax.UUCP (Michael Greim)
Newsgroups: comp.unix.questions,comp.bugs.misc
Subject: Re: Vi bug
Summary: It is a bug. I am trying to fix it.
Message-ID: <722@sbsvax.UUCP>
Date: 17 Apr 89 16:35:53 GMT
References: <1001@philmds.UUCP>
Followup-To: comp.bugs.misc
Organization: Universitaet des Saarlandes, Saarbruecken, W-Germany
Lines: 28

In article <1001@philmds.UUCP>, leo@philmds.UUCP (Leo de Wit) writes:
< Maybe someone has been bitten by this one before, but anyway, here it
< goes (reproducable at least both on Ultrix 2.x and SUNOS 3.5):
< 
< Create a file with at least one line that wraps (depending on your
< terminal / window, probably a line of over 80 chars).
< 
< Now type '/' (search) followed by windowsize+1 dots (so probably 81).
< 
< Surprise! You probably get a corrupted display (even ^L won't help). By
< pressing 'n' a few times I managed to get an internal vi error (it goes
< back to ex mode). If it matters: my wrapmargin is set to 0.
< 
[...]
< 	 Leo.

It is a bug. I had it on 4.3BSD, SUN OS and Ultrix.
I will try to find the bug. As I do this in my sparetime it may take some
days. It may also be one of those bugs, for which you must rewrite large
parts of vi.
Watch this space.

	-mg
-- 
email : greim@sbsvax.informatik.uni-saarland.dbp.de
  (some mailers might not like this. Then use greim@sbsvax.uucp)
  or  : ...!uunet!unido!sbsvax!greim
# include <disclaimers/std.h>