From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25535 invoked from network); 28 May 2009 19:04:08 -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 19:04:08 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 88987 invoked from network); 28 May 2009 19:04:01 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 28 May 2009 19:04:01 -0000 Received: (qmail 20111 invoked by alias); 28 May 2009 19:03:53 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 27012 Received: (qmail 20088 invoked from network); 28 May 2009 19:03:51 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 28 May 2009 19:03:51 -0000 Received: from smtprelay11.ispgateway.de (smtprelay11.ispgateway.de [80.67.31.34]) by bifrost.dotsrc.org (Postfix) with ESMTP id D698D8027106 for ; Thu, 28 May 2009 21:03:47 +0200 (CEST) Received: from [212.117.84.96] (helo=fsst.voodoo.lan) by smtprelay11.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1M9ktH-0006xy-0L for zsh-workers@sunsite.dk; Thu, 28 May 2009 21:03:47 +0200 Received: from hawk by fsst.voodoo.lan with local (Exim 4.69) (envelope-from ) id 1M9kt8-0008Jb-8a for zsh-workers@sunsite.dk; Thu, 28 May 2009 21:03:38 +0200 Date: Thu, 28 May 2009 21:03:38 +0200 From: Frank Terbeck To: zsh-workers@sunsite.dk Subject: Re: PATCH: Add CORRECT_NOCOMPSYS option Message-ID: <20090528190338.GC3315@fsst.voodoo.lan> Mail-Followup-To: zsh-workers@sunsite.dk References: <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=iso-8859-1 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-Df-Sender: 430444 X-Virus-Scanned: ClamAV 0.94.2/9401/Thu May 28 18:24:00 2009 on bifrost X-Virus-Status: Clean Greg Klanderman : > >>>>> 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. [...] Yes, that was my guess. Completion. > > 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 "_". Since I don't use matcher-lists, I cannot comment any further. Compsys experts will have to take on that one. :) > 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. That's my point. CORRECT_IGNORE has *nothing* to do with completion. It's about correction. That is precisely why I was asking about what Richard meant by 'final goal', because the thread initially had nothing to do with completion. Final goal in completion - based on what you described - will have to be solved within compsys. Final goal in correction (for the problem I described), can be achieved by what CORRECT_IGNORE provides. If someone wants more control in _correction_ than that, that someone would probably have to reimplement the correction code into a more flexible system (maybe even function based - like compsys). But I doubt it would be worth it. > 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? Could a compsys guru shed some light on this? :) Regards, Frank -- In protocol design, perfection has been reached not when there is nothing left to add, but when there is nothing left to take away. -- RFC 1925