From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-19717-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 545 invoked by alias); 8 Jan 2015 17:12:30 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 19717
Received: (qmail 29474 invoked from network); 8 Jan 2015 17:12:28 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.2
X-Authority-Analysis: v=2.1 cv=X+5rdgje c=1 sm=1 tr=0
 a=rhK92a8tbrCHi84BnR0MuQ==:117 a=rhK92a8tbrCHi84BnR0MuQ==:17 a=Hpgzp-inWqAA:10
 a=IkcTkHD0fZMA:10 a=YR4_K0clAAAA:8 a=ou43M76a9Hq7pzUqAB0A:9 a=QEXdDO2ut3YA:10
Message-id: <54AEBA78.8040302@eastlink.ca>
Date: Thu, 08 Jan 2015 09:12:24 -0800
From: Ray Andrews <rayandrews@eastlink.ca>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.3.0
MIME-version: 1.0
To: zsh-users@zsh.org
Subject: Re: completion
References: <5488D414.6010300@eastlink.ca> <30453.1418258082@thecus.kiddle.eu>
 <5488F0AC.2040901@eastlink.ca> <141210214454.ZM12261@torch.brasslantern.com>
 <5489C8F4.8030703@eastlink.ca> <141211092824.ZM13349@torch.brasslantern.com>
 <5489F1BC.5000900@eastlink.ca> <20150107150109.GA14088@ypig.lip.ens-lyon.fr>
 <CAH+w=7YQ=VrWFjCXn4q7U48e3R+eNTF9xihHBf-oFDYTVR_zGQ@mail.gmail.com>
 <20150108004323.GA7954@xvii.vinc17.org>
 <CAH+w=7ZPnjtZQJLM012ZJFx-zj7pFLzVivEG+Q=vixLGnjrM5g@mail.gmail.com>
In-reply-to:
 <CAH+w=7ZPnjtZQJLM012ZJFx-zj7pFLzVivEG+Q=vixLGnjrM5g@mail.gmail.com>
Content-type: text/plain; charset=utf-8; format=flowed
Content-transfer-encoding: 7bit

On 01/07/2015 09:26 PM, Bart Schaefer wrote:
> On Wed, Jan 7, 2015 at 4:43 PM, Vincent Lefevre <vincent@vinc17.net> wrote:
>> But the ambiguity shouldn't be intentional.
> Nevertheless, it is.
...

If * matches everything, then this could mean [any of]

   :completion:[any function]:complete:[any cmd]:[any arg]:[any tag]
   :completion:[any function]:[any completer]:complete:[any arg]:[any tag]
   :completion:[any function]:[any completer]:[any cmd]:complete:[any tag]

> You're correct, it could.  But "matcher-list" also has to match, and
> THAT only happens in one of those three cases, so there's no need to
> constrain the pattern any further (unless you WANT to; refer to my
> car-cover analogy).
Ah!  So I find myself reaching for a better word. 'ambiguity' = 
uncertainty or confusion. What we have here, then, is not confusion, but 
rather a carefully
expanded space of possibilities, or freedoms.

    $ ls zsh* ... the asterisk is not ambiguous, we know *exactly* what 
is means.
It expands the matching space, but that is not an ambiguity because we know
exactly what the rules are.  If our zstyle asterisks do something 
analogous, then they are not an ambiguity.  Right? Wrong?