From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2245 invoked from network); 14 Jun 1998 19:58:03 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 14 Jun 1998 19:58:03 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id PAA00855; Sun, 14 Jun 1998 15:54:19 -0400 (EDT) Resent-Date: Sun, 14 Jun 1998 15:54:19 -0400 (EDT) From: TGAPE! Message-Id: <199806141357.NAA02238@tgape.ed.vnet> Subject: Re: 'remove slash' bug To: zsh-workers@math.gatech.edu Date: Sun, 14 Jun 1998 13:56:52 +0000 (GMT) In-Reply-To: <199806080356.UAA20692@bebop.clari.net> from "Wayne Davison" at Jun 7, 98 08:56:34 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: <"555BF3.0.FD.gf2Xr"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/4114 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Wayne Davison wrote: > > Timothy J Luoma writes: >> However, there are times when I am in the middle of a path and do >> control-e to get to the end of the line, and the / I put in (and >> wanted) is removed. > > I haven't managed to reproduce this problem, but I have been meaning > to look into a problem with the yank command being used right after > an auto-added slash. I think the yank should leave the slash there, > but perhaps it should be made to depend on what text is being yanked > (i.e. make it work just like the yanked text had been typed). I can reproduce it. Type /usr This is actually a more general problem, because it doesn't have to be a slash character which gets deleted. It'll be whatever would be deleted with a backspace. I saw this quite some time ago, but was too busy to submit a full trouble report. I'm running 3.1.1; I've seen it with 3.1.2 and 3.0.5. (No, I can't remember why I backed out of 3.1.2, yes, I do feel it's time to upgrade.) Ed