Xref: utzoo comp.bugs.sys5:1304 comp.editors:1669
Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!pdn!palan!sherpa!rac
From: rac@sherpa.UUCP (Roger Cornelius)
Newsgroups: comp.bugs.sys5,comp.editors
Subject: Re: Obscure Vi bug?
Message-ID: <295@sherpa.UUCP>
Date: 19 Jul 90 20:49:59 GMT
References: <798@intelhf.hf.intel.com>
Followup-To: comp.bugs.sys5
Organization: Personal System Computing,  St. Petersburg, FL
Lines: 14

From article <798@intelhf.hf.intel.com>, by fredch@starlite.hf.intel.com:
> Has anyone else experienced this?  I have AT&T/Intel Unix V/386 on my box:
> 
> Take a 50 line file (not sure if 50-line specific, but that's where I found it).
> Go to 2 lines below the bottom line using the G command.  For example, under
> TERM=xterm, go to line 25; under TERM=AT386 or TERM=vtpc, go to line 26.
> Then type ^B.  It will beep.  Then, type j.  Suddenly the current line will
> be copied onto line 1, and your file just got modified.

This also occurs with the vi on SCO UNIX V3.2.0, which, when given the
:version command reports SVR3.1.  It doesn't appear to be file length
specific.
-- 
Roger A. Cornelius          rac@sherpa.UUCP         uunet!sherpa!rac