From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-29263-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 20549 invoked by alias); 13 May 2011 18:23:36 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 29263
Received: (qmail 1913 invoked from network); 13 May 2011 18:23:22 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW autolearn=ham
	version=3.3.1
Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.google.com designates 209.85.220.171 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:cc:content-type;
        bh=PXZSG6U9z+UQ2Hur1R2NkzT4P81WTKcY6ga24zWFXZQ=;
        b=ZOfFLK/uAjssPwkHYSXUW4gatVfpvebwGbDe4SkBnFtxsLKZ1onQPnWAC4VqsmQCI/
         sKanfcYJRKINBY/Ge733mYNPhWv4CNKDJveaWI0ToggwliYyhBe9eAIqv6ZEUc3t7A83
         dgd60cWJrFOZjs1xy96WYb2mcYTkxA8Nmxbd8=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=EZBzLGxz4mVaK3ZFqyF3NIxuhboZajL1mAGHaDx8+BMv2+OFM3pHSSyPu53tt4JDgm
         BDuuCqrB19+XoUesiQTgqwC3vuriCArb5XXiBbYskFSYTrAqOtrqDG7DjV6rYp48UQOB
         yzeFQ4STU7XBWim+P8yB4KyuedVlC90hkf+ok=
MIME-Version: 1.0
In-Reply-To: <20110513191710.657d2f61@pws-pc.ntlworld.com>
References: <BANLkTikqnR3pJk8FzRT6Qo9J+wTMGSnycQ@mail.gmail.com>
	<20110513191710.657d2f61@pws-pc.ntlworld.com>
Date: Fri, 13 May 2011 20:23:15 +0200
Message-ID: <BANLkTi=KyDfiM1YqXR0q1w-PxiAeQ0thdQ@mail.gmail.com>
Subject: Re: squeeze-slashes false not working?
From: Mikael Magnusson <mikachu@gmail.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh workers <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8

On 13 May 2011 20:17, Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> On Thu, 12 May 2011 19:18:26 +0200
> Mikael Magnusson <mikachu@gmail.com> wrote:
>> Another old mail:
>> """
>> estragib noted on irc that
>> 21:28:58 <estragib> completing ~/d/p/t/i.<TAB> works for
>> ~/dev/prj/test/index.html, as does ~/d/*/*/ind<TAB>. i vaguely remember
>> seeing a setting somewhere that will allow ~/d///ind<TAB> but can't find
>> it again. help? :)
>>
>> and it seems that setting squeeze-slashes to true or false has no
>> effect, the slashes are always squeezed. But it works in zsh -f.
>> """
>>
>> But now I can't reproduce it working in zsh -f. At best it jumps back
>> to the first doubleslash and completes at that point. Maybe another
>> option is interfering, any idea which one if so?
>
> That's the standard feature that it tries to expand path segments before
> the first.  It can be turned off by setting the style path-completion to
> false, although what setting it to false does is to allow _path_files to
> skip a prefix of the file that already exists, and I'm not sure what
> happens if there are multiple slashes there.

Hm, with that set, zsh -f starts acting like with my .zshrc, ie as if
I only had one slash. Does ls /////<tab> just show stuff in / for you
too? The documentation for squeeze-slashes says it should act like I
typed ls /*/*/*/*/<tab>.

-- 
Mikael Magnusson