From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Zsh Users <zsh-users@sunsite.dk>
Subject: Re: compsys issues
Date: Wed, 27 Oct 2004 17:43:51 +0200 [thread overview]
Message-ID: <16515.1098891831@trentino.logica.co.uk> (raw)
In-Reply-To: <20041027145444.GB10003@DervishD>
DervishD wrote:
>
> OK, but that doesn't solve the problem I explained below. And I
> assumed that I must use $PREFIX :? I don't understand why I must
> remove the last path element from PREFIX :?
Sorry, I probably only confused things by mentioning that point. It only
really matters if you use matching control. For example, if you want
case-insensitive matching. If $PREFIX contains `mo', mo* would not match
a file named More while just adding * as matches allows the completion
matching control to decide for itself which files match.
> That works perfectly, thanks a lot :) The only part I didn't
> understand was the -W flag. I mean, the manual says this flag adds the
> string to the WORDS, and I though that the process was:
-W only controls the way the -f option works. The string is added to the
WORDS purely for the purpose of finding out whether the match refers to
a regular file, a directory or whatever. -W has no effect on what the
list of matches will be. Try removing the -W and -f options from compadd
and use `-S /' instead if you want.
> But if I understand correctly, the string that follows '-W' is
> added *before* compadd does the matching, am I wrong?
Whether it is before or after makes no difference. The string following
-W has nothing to do with matching.
Oliver
next prev parent reply other threads:[~2004-10-27 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 13:26 DervishD
2004-10-27 14:08 ` Oliver Kiddle
2004-10-27 14:54 ` DervishD
2004-10-27 15:43 ` Oliver Kiddle [this message]
2004-10-27 16:07 ` DervishD
2004-10-27 16:44 ` DervishD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16515.1098891831@trentino.logica.co.uk \
--to=okiddle@yahoo.co.uk \
--cc=zsh-users@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).