Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160619091803.ZM1176@torch.brasslantern.com>
Date: Sun, 19 Jun 2016 09:18:03 -0700
In-Reply-To: <23451.1466284625@thecus.kiddle.eu>
Comments: In reply to Oliver Kiddle <okiddle@yahoo.co.uk>
        "PATCH: allow default match specs to be disabled (was Re: [PATCH v4] zsh localedef completion)" (Jun 18, 11:17pm)
References: <57504DEC.9000101@redhat.com> 
	<2aa4c678-6d5e-0614-7aff-e374c3108ba3@gmx.com> 
	<5312.1465896712@thecus.kiddle.eu> 
	<fc6b9fc8-e37f-1756-ed08-c87d5ffd7317@gmx.com> 
	<23451.1466284625@thecus.kiddle.eu>
To: zsh-workers@zsh.org
Subject: Re: PATCH: allow default match specs to be disabled (was Re: [PATCH v4] zsh localedef completion)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Jun 18, 11:17pm, Oliver Kiddle wrote:
}
} Turns out it isn't hard to do.
} 
} This patch uses x: as the token. Any thoughts on that or alternative
} suggestions?

My only other thought would be a single hyphen or a single exclamation
point, for similarity with the tag-order style, 
 
} There's nothing in the documentation to suggest that the ordering of
} matching specifications has any effect. Is anyone aware of whether it
} perhaps does?

I would expect that it does, for a number of reasons:
  * you can group specs to be tried "all the same time" together in
    a single quoted string, or have several strings that are to be
    tried separately
  * specs can begin with a "+" to append them to an existing spec
  * it matters that the global matcher is prepended to matcher-list
    rather than appended

What is it that leads you to think it's order-independent?

} The documentation of the matcher style was perhaps deceptive in
} indicating that it is tried before matcher-list. The value is merely
} placed before those from matcher-list.

I have this comment in my .zshrc:

# Matching
# 1. Try completion with no alterations (i.e., literal match is best)
# 2. Match substrings separated by dashes, dots, underscores, commas
# 3. As (2) but case-insensitively
# 4. As (2) but allow arbitrary stuff at the beginning of the result
zstyle ':completion:*' matcher-list '' 'r:|[-._,]=** r:|=**' \
    'm:{[:lower:][:upper:]}={[:upper:][:lower:]} r:|[-._,]=** r:|=**' \
    'r:|[-._,]=** r:|=** l:|=*'

The behavior I see from completion leads me to believe that later
matchers are not tried if earlier matchers generate a result, e.g.,
"literal match is best" => put empty matcher first.

Maybe I'm misunderstanding your question.