From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21299 invoked from network); 1 Jun 1998 21:58:54 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 1 Jun 1998 21:58:54 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id RAA18176; Mon, 1 Jun 1998 17:53:08 -0400 (EDT) Resent-Date: Mon, 1 Jun 1998 17:53:08 -0400 (EDT) Message-Id: <199806012153.OAA05718@bebop.clari.net> To: Zefram Cc: zsh-workers@math.gatech.edu Subject: Re: zsh-workers: zsh-3.1.4 In-reply-to: zefram's message of Mon, 01 Jun 1998 09:19:24 +0100. <199806010819.JAA27897@diamond.tao.co.uk> Date: Mon, 01 Jun 1998 14:53:57 -0700 From: Wayne Davison Resent-Message-ID: <"Wip-D2.0.xR4.4BoSr"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/4030 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Zefram writes: > 3969 fix spaceinline() to fix yank > I think spaceinline() already has the correct behaviour, and > callers that invoke the boundary case should explicitly implement > the behaviour they actually want. No, spaceinline() is definitely broken. To see this, it is only necessary to set the point and type some characters. The easiest way to do this is to start with an empty line (which has the point set to the start of the line), type a few characters, and type Ctrl-X Ctrl-X -- the curor doesn't budge (it should have gone to the start of the line). That's because spaceinline() keeps bumping the point forward when it shouldn't. Having a >= in spaceinline() is wrong -- it should be just >. ..wayne..