From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-17977-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 25964 invoked by alias); 10 Sep 2013 16:31:29 -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: 17977
Received: (qmail 26211 invoked from network); 10 Sep 2013 16:31:23 -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=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	SPF_HELO_PASS autolearn=ham version=3.3.2
Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts)
X-AuditID: cbfec7f4-b7f0a6d000007b1b-73-522f4957f83a
Date: Tue, 10 Sep 2013 17:31:18 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: Bart Schaefer <schaefer@brasslantern.com>, zsh-users@zsh.org
Subject: Re: custom completion for listing *.tex is not working
Message-id: <20130910173118.517c38fc@pwslap01u.europe.root.pri>
In-reply-to: <130910080852.ZM9661@torch.brasslantern.com>
References:
 <CAMXWGTwZB9wP4YbuW703sBErWZhRYrb6YpWZ2mGKqtGo08KOVg@mail.gmail.com>
 <130903073216.ZM27351@torch.brasslantern.com>
 <CAMXWGTyaZ+YR6pZG8=BLThjNhjZtO1kzW03fRHv3EMeaNk=_ug@mail.gmail.com>
 <130910080852.ZM9661@torch.brasslantern.com>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFprBLMWRmVeSWpSXmKPExsVy+t/xK7rhnvpBBle2y1rsn/6QxWLHyZWM
	Dkwe91dNYfVYdfADUwBTFJdNSmpOZllqkb5dAlfG31fz2QrusFSc2HaQsYHxAnMXIyeHhICJ
	xLp/LUwQtpjEhXvr2boYuTiEBJYySjy//48FwulnkpjVdAGsikVAVeLLzj4wm03AUGLqptmM
	ILaIgIPE5o5DbCC2sIC9xKMTx8A28ALZD6++ZQGxOQUsJR7M3cUIMfQHo8SRmQ1gzfwC+hJX
	/36COsNeYuaVM4wQzYISPybfA2tmFtCS2LytiRXClpfYvOYt8wRGgVlIymYhKZuFpGwBI/Mq
	RtHU0uSC4qT0XEO94sTc4tK8dL3k/NxNjJDQ/LKDcfExq0OMAhyMSjy8N+T0g4RYE8uKK3MP
	MUpwMCuJ8E51AgrxpiRWVqUW5ccXleakFh9iZOLglGpgNFueIe6aUMiw4iaH/Jsez5K0U28X
	H5Xv7/3qdU5Xs1kjujQ3siy66mLq3yO88dOm7ih/qrlv/xQeydXloS66YtHrTiyzmZyx5L/G
	lKNcti4OU49cVcouOm8af0pPxD/48Bf/eXUr7SuXTL9+3TtWf7Gk1EZL7phpkxkuvfN7cnH5
	4/XbPWY2KbEUZyQaajEXFScCADeJHvYrAgAA

On Tue, 10 Sep 2013 08:08:52 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> What the manual doesn't make clear is that file-patterns may have its
> values combined in sets the same way tag-order might.

Isn't that what this bit is saying?

  The tags of all strings in the value will be offered  by  _files
  and  used  when  looking  up other styles.  Any tags in the same
  word will be offered at the same time and  before  later  words.
  If no `:tag' is given the `files' tag will be used.

'Word' is perhaps a little confusing where it means 'command line
argument'.

pws