Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!lambert
From: lambert@mcvax.uucp (Lambert Meertens)
Newsgroups: comp.unix.wizards
Subject: Re: vi bug?
Message-ID: <7157@boring.mcvax.UUCP>
Date: Fri, 21-Nov-86 03:02:11 EST
Article-I.D.: boring.7157
Posted: Fri Nov 21 03:02:11 1986
Date-Received: Fri, 21-Nov-86 21:48:20 EST
References: <939@brl-adm.ARPA>
Reply-To: lambert@boring.uucp (Lambert Meertens)
Organization: CWI, Amsterdam
Lines: 22
Summary: Amplification
Apparently-To: rnews@mcvax


In article <939@brl-adm.ARPA> stanonik@nprdc.arpa (Ron Stanonik) writes:
> One of our users pointed out a problem with vi [..]:
> The problem is a failure of vi to properly "put" a large (half a line
> or so) chunk of text into another line when two conditions exist: 1) The
> wrapmargin is set to some non-zero value; 2) The put is done near the end
> of the line (i.e., the inserted text will cross the wrapmargin).

A third condition is that the text in the put buffer contains spaces.  What
seems to happen is that a space on which wrap should occur AND the character
following it are not inserted.  Instead, the non-space characters following
each such space are interpreted as commands(!), in the reverse order of that
in which they occur.

This annoying bug has been in vi as long as I can remember and has persisted
up through BSD 4.3.  It has been signalled before on the net.  It is
probably just a silly coding error that should be easy to spot (assuming
you know your way around in the vi code), what with such specific and
repeatable behaviour.

-- 

Lambert Meertens, CWI, Amsterdam; lambert@mcvax.UUCP