From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23105 invoked from network); 28 May 2009 18:54:04 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 Received: from new-brage.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.254.104) by ns1.primenet.com.au with SMTP; 28 May 2009 18:54:04 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 82350 invoked from network); 28 May 2009 18:45:11 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 28 May 2009 18:45:11 -0000 Received: (qmail 8051 invoked by alias); 28 May 2009 18:44:53 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 27011 Received: (qmail 8024 invoked from network); 28 May 2009 18:44:51 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 28 May 2009 18:44:51 -0000 Received: from QMTA06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by bifrost.dotsrc.org (Postfix) with ESMTP id D926E8027106 for ; Thu, 28 May 2009 20:44:34 +0200 (CEST) Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA06.westchester.pa.mail.comcast.net with comcast id x50j1b00D0ldTLk566kab7; Thu, 28 May 2009 18:44:34 +0000 Received: from smtp.klanderman.net ([98.217.254.247]) by OMTA04.westchester.pa.mail.comcast.net with comcast id x6ka1b00c5M2Np63Q6kaHe; Thu, 28 May 2009 18:44:35 +0000 Received: from lwm.klanderman.net (unknown [192.168.100.50]) by smtp.klanderman.net (Postfix) with ESMTP id 7A8ABB30144 for ; Thu, 28 May 2009 14:44:33 -0400 (EDT) Received: by lwm.klanderman.net (Postfix, from userid 500) id 5D7E29FC61B; Thu, 28 May 2009 14:44:33 -0400 (EDT) From: Greg Klanderman To: zsh-workers@sunsite.dk Subject: Re: PATCH: Add CORRECT_NOCOMPSYS option Reply-To: gak@klanderman.net Date: Thu, 28 May 2009 14:44:33 -0400 In-Reply-To: <20090528092514.GA3315@fsst.voodoo.lan> (Frank Terbeck's message of "Thu, 28 May 2009 11:25:14 +0200") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (linux) References: <1238890030-4683-1-git-send-email-ft@bewatermyfriend.org> <090404193718.ZM19801@torch.brasslantern.com> <20090405191304.1908fca8@pws-pc> <090405151115.ZM13159@torch.brasslantern.com> <20090406100929.505617e2@news01> <2d460de70905270930j681da6a5kf7848d67d89f0c69@mail.gmail.com> <20090527175941.3bbe2eba@news01> <2d460de70905280148iebfcegcb4143c33e510efd@mail.gmail.com> <20090528092514.GA3315@fsst.voodoo.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: ClamAV 0.94.2/9401/Thu May 28 18:24:00 2009 on bifrost X-Virus-Status: Clean >>>>> Frank Terbeck writes: > The final goal for what? Not completing all the stupid completion widget functions starting with "_" at a shell prompt where they are totally irrelevant. It'd still not be perfect; ideally they'd be in some other namespace or something and therefore never be completed, but various helper functions of my own would still be completable if I explicitly type the "_". > For completion (without looking at it in detail), I think what Greg > wants could be done with the _ignore completer. > : > So, when you're talking about a final goal, IMHO, CORRECT_IGNORE is > quite a reasonable solution. Neither of these mechanisms do what I described. If you allow substring completion, i.e. | zstyle ':completion:*' matcher-list '' 'm:{a-zA-Z}={A-Za-z}' '+ l:|=* r:|=*' then even with the 'ignored-patterns' zstyle set to '_*', if you try to complete something which has no non-ignored matches, it will then fall back to not ignoring those patterns, and will complete to something that starts with "_" even when there was no "_" before you hit . If you remove the _ignore completer, then you can never complete a function starting with "_". For CORRECT_IGNORE, just look back to Richard's original question in this thread - with that setting you can *never* complete something that matched the pattern, which is not what you want. Even with the 'matcher-list' setting for substring completion, file completion of files starting with '.' does work as I want. Can someone point me to where that is handled? cheers, Greg