From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15683 invoked from network); 9 Sep 2004 15:00:29 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 9 Sep 2004 15:00:29 -0000 Received: (qmail 24109 invoked from network); 9 Sep 2004 15:00:21 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 9 Sep 2004 15:00:21 -0000 Received: (qmail 27903 invoked by alias); 9 Sep 2004 15:00:09 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 20342 Received: (qmail 27883 invoked from network); 9 Sep 2004 15:00:09 -0000 Received: from unknown (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 9 Sep 2004 15:00:09 -0000 Received: (qmail 23333 invoked from network); 9 Sep 2004 14:59:10 -0000 Received: from moonbase.zanshin.com (64.84.47.139) by a.mx.sunsite.dk with SMTP; 9 Sep 2004 14:59:07 -0000 Received: from toltec.zanshin.com (toltec.zanshin.com [64.84.47.166]) by moonbase.zanshin.com (8.13.1/8.13.1) with ESMTP id i89Ex3On004720; Thu, 9 Sep 2004 07:59:03 -0700 Date: Thu, 9 Sep 2004 07:59:02 -0700 (PDT) From: Bart Schaefer Reply-To: zsh-workers@sunsite.dk To: Clint Adams cc: zsh-workers@sunsite.dk, 270632-submitter@bugs.debian.org Subject: Re: Bug#270632: zsh: Completion and spaces In-Reply-To: <20040908235639.GB6785@scowler.net> Message-ID: References: <20040908115321.GA2417@larve.net> <20040908180950.GC25987@scowler.net> <20040908194101.GD2775@larve.net> <20040908202633.GA3130@scowler.net> <20040908235639.GB6785@scowler.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.63 on a.mx.sunsite.dk X-Spam-Level: X-Spam-Status: No, hits=0.0 required=6.0 tests=none autolearn=no version=2.63 X-Spam-Hits: 0.0 On Wed, 8 Sep 2004, Clint Adams wrote: > > No, it isn't. See zsh-users/7841 for discussion, and the final three > > paragraphs therein for suggested repair. > > Ah. Is there a downside to the LBUFFER+='' workaround? Only that it always disables auto-suffix-removal. E.g., if $LBUFFER ends in a slash which was added as a completion suffix, and the first character of the word to be inserted is also a slash, then normally the suffix would be deleted in order that the slash not become doubled; but with the work- around, you get the double slash.