From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-39378-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 19188 invoked by alias); 18 Sep 2016 01:34:50 -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: 39378
Received: (qmail 26809 invoked from network); 18 Sep 2016 01:34:50 -0000
X-Qmail-Scanner-Diagnostics: from nm11-vm7.bullet.mail.ir2.yahoo.com by f.primenet.com.au (envelope-from <okiddle@yahoo.co.uk>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(212.82.96.168):SA:0(0.0/5.0):. 
 Processed in 0.548929 secs); 18 Sep 2016 01:34:50 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=FREEMAIL_FROM,SPF_PASS,
	T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1
X-Envelope-From: okiddle@yahoo.co.uk
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.mail.yahoo.com designates 212.82.96.168 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048; t=1474162087; bh=YjQXqepiyJa76/SlZ3kXxYcPslNosXYZQ2W1gGlah1E=; h=In-reply-to:From:References:To:Subject:Date:From:Subject; b=QtSmS/g2jDolEJOM7bLwJtJUHXwyDSKxu6Uiac2xN7zWk34YXh0sdDlfdT9+5a4V49mSq0u24vRob1WVeSt/iTmU0ZQ0zsuanrOZznl/Johd/H4JHDMLdSmRLPbjG/BDiILPtup2rPdeT2WPuCi0n/lxYeoLZSWWEML/2TpwoBMn37oxy4amup9u5hdCrQqQa2W2kC5zT7kHD2ENZb5r6WE/ejk/Uone7/KQI4QZDv/QMrlP81Jf3hU+KkszdKNKLYQopsCnJzqUQOyZR3cqveYimPc3TS6HjVwdC/SU7fYafl/9OrbNv8S5EV0TOjC3TXGgVwnw0RowZkpWVsCcHA==
X-Yahoo-Newman-Id: 805018.4124.bm@smtp138.mail.ir2.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: Nzew.tQVM1l0U58RQpxvphpsGakrULLuWc2GLZJKtosaMmx
 ceOaKuc1PhV1pceqanFxtLM340RV1t2llv9Tl2e5tfmNIJulCP21ha5Gl1Np
 ddcfCG8Dt2.kDbZTOwUYBhpWGAKq9f5OTzsdnhrrcaoo3SYN07kWuiE_ImzA
 YFCmXvxySAp12tkUM343ouIpVWSNUr7CVD_j5z5dbrSXCThP.Pe2f7PNKfnX
 1Ab5cs7PaddxdjcVJEkFm9VyT2eic8.I04Jv4Co8D6ORVzyG157KSeF9yY3w
 SI8.OTsCm1SkKo3DKEpG.hRyizRX.8nlm0oxdhRBWblm3MHpDDI7LWZvdE_d
 RM3yvjIHDqa09aqMXLomq5NRuHDONV7hAu5tVgBjl0FgAqb3SbC1tVrzgOpz
 HR8UehAfhSyaDHrkiq1dY7PprTNJJcm8YvAgx6lPtWYVNBVEa1X_r.jtvXqZ
 pt2u8gx6vqobBifjkf5.Oeln_gqKg6sqScMEqLO9LC.hKPryyKfD2.jsHpTr
 kWbAWRqV9Ga2FiMDbMm4JJPfophnQRFwWV3MDglFbeq8-
X-Yahoo-SMTP: opAkk_CswBAce_kJ3nIPlH80cJI-
In-reply-to: <20160917063258.GA26826@fujitsu.shahaf.local2>
From: Oliver Kiddle <okiddle@yahoo.co.uk>
References: <20160917063258.GA26826@fujitsu.shahaf.local2>
To: zsh-workers@zsh.org
Subject: Re: 'compadd -P' matches $PREFIX greedily
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <69989.1474162087.1@hydra.kiddle.eu>
Content-Transfer-Encoding: 8bit
Date: Sun, 18 Sep 2016 03:28:07 +0200
Message-ID: <69990.1474162087@hydra.kiddle.eu>

Daniel Shahaf wrote:
> The following completion function:
>
> % compdef 'compadd -P p_____ papa mama nana aaaa' f
> % f pa<TAB>   → p_____aaaa

Out of interest, was there a real prefix where you came across this.
I was trying to think of more realistic prefixes to see how this
might affect them:

% compdef 'compadd -P file:// /papa //mama /nana aaaa filter' f

before: f fil<tab> → file://
after : f fil<tab> → file://filter

That now seems a bit too aggressive.

How about allowing the longest common prefix to be equal to either
the -P prefix or equal to $PREFIX.

Oliver