From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27110 invoked by alias); 22 May 2012 06:35:16 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 17103 Received: (qmail 2216 invoked from network); 22 May 2012 06:35:14 -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=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <120521233507.ZM1136@torch.brasslantern.com> Date: Mon, 21 May 2012 23:35:07 -0700 In-reply-to: <20120522050158.GC26384@lorien.comfychair.org> Comments: In reply to Danek Duvall "Re: completion oddity" (May 21, 10:01pm) References: <20120521214023.GB10763@lorien.comfychair.org> <120521194232.ZM990@torch.brasslantern.com> <20120522050158.GC26384@lorien.comfychair.org> <20120522051617.GD26384@lorien.comfychair.org> In-reply-to: <20120522051617.GD26384@lorien.comfychair.org> Comments: In reply to Danek Duvall "Re: completion oddity" (May 21, 10:16pm) X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: completion oddity MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On May 21, 10:01pm, Danek Duvall wrote: } } I did a quick test with the matcher-list zstyle, though, but couldn't } get it to work (without the -M "" in _k). Two things ... } zstyle ":completion::complete:k::" matcher-list "" (1) The matcher-list is looked up very early in completion. The context isn't yet this specific at that point. (I think this is in the FAQ.) } zstyle ":completion:*" matcher-list "" The matcher-list style is only used when it is not empty! _description: [[ -n "$_matcher" ]] && opts=($opts -M "$_matcher") So you can't use matcher-list to turn off matching, only to modify it. } I also took another look through the GNU tar options for a similar } situation, and found Hmm, when I try gtar completion I get _arguments:comparguments:312: invalid option definition: -[0-7]lmh[specify drive and density] So I'm not really able to reproduce this. } gtar --show--names } } and it beeps and moves me to between the second double-hyphen, then after } another beep, starts cycling between the two. If I just have "--show" } there, then it ends up cycling among four alternatives. Do all four alternatives have the same number of hyphens?