From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26489 invoked from network); 2 Jun 1998 07:34:31 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 2 Jun 1998 07:34:31 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id DAA27388; Tue, 2 Jun 1998 03:30:27 -0400 (EDT) Resent-Date: Tue, 2 Jun 1998 03:30:27 -0400 (EDT) From: Zefram Message-Id: <199806020731.IAA20152@taos.demon.co.uk> Subject: Re: zsh-workers: zsh-3.1.4 To: wayne@clari.net (Wayne Davison) Date: Tue, 2 Jun 1998 08:31:08 +0100 (BST) Cc: zefram@tao.co.uk, zsh-workers@math.gatech.edu In-Reply-To: <199806012153.OAA05718@bebop.clari.net> from "Wayne Davison" at Jun 1, 98 02:53:57 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"L-Tdw3.0.th6.IewSr"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/4033 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Wayne Davison wrote: >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 >. So the mark should be attached to the preceding character, rather than the following? If that is the correct semantic then spaceinline() is broken. -zefram