Xref: utzoo comp.bugs.sys5:1299 comp.unix.i386:7038 comp.unix.questions:23909 comp.unix.xenix:12476
Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!sdd.hp.com!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!mcsun!unido!sbsvax!greim
From: greim@sbsvax.cs.uni-sb.de (Michael Greim)
Newsgroups: comp.bugs.sys5,comp.unix.i386,comp.unix.questions,comp.unix.xenix
Subject: Re: Obscure Vi bug?
Summary: It's not a BSD vi bug, it seems to be SYS V specific.
Message-ID: <5575@sbsvax.cs.uni-sb.de>
Date: 20 Jul 90 13:19:45 GMT
References: <798@intelhf.hf.intel.com> <846@mwtech.UUCP>
Followup-To: comp.bugs.sys5
Organization: Universitaet des Saarlandes, Saarbruecken, W-Germany
Lines: 25

In article <846@mwtech.UUCP>, martin@mwtech.UUCP (Martin Weitzel) writes:
= In article <798@intelhf.hf.intel.com> fredch@starlite.hf.intel.com () writes:
= >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.
= 
= Just tried this with ISC 386/ix 2.0.2 and SCO XENIX V. Same bug here.
= I produced it in the following way:
= 
[... detailed description of how to reproduce bug ...]

I tried it on several machines with several 24 and 25 line terminals.
I could not reproduce the bug. As all these systems are BSD or -related,
it seems that the bug is specific to the SYS V version of vi.

	-mg
-- 
 .-. .-.  .-.  Michael Greim
(   X   )( __) e-mail : greim@cs.uni-sb.de
 \ / \ /  \ /  or     : ...!uunet!unido!sbsvax!greim
  ~   ~    ~