From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17718 invoked by alias); 3 Mar 2011 16:54:57 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 28847 Received: (qmail 23920 invoked from network); 3 Mar 2011 16:54:55 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) 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.1 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <110303085435.ZM12072@torch.brasslantern.com> Date: Thu, 03 Mar 2011 08:54:35 -0800 In-reply-to: Comments: In reply to Greg Klanderman "Re: PATCH: zstyle to control completion of functions/parameters beginning with underscore" (Mar 3, 10:33am) 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> <7658.1299027908@thecus> <110302153027.ZM10605@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: PATCH: zstyle to control completion of functions/parameters beginning with underscore MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Mar 3, 10:33am, Greg Klanderman wrote: } Subject: Re: PATCH: zstyle to control completion of functions/parameters b } } Easiest is to just use 'zstyle -t' in the new use cases and leave the } 'zstyle -T' as-is in the existing twelve uses. That's probably fine. I was just trying to avoid the situation where the doc has to keep track of which cases default to true and which ones default to false. That is, there seem to be three choices from the doc point of view: (1) Explicitly list where it defaults to true and where false. (2) Stop claiming there's any default at all, and say that when it is not set, every context chooses the most-commonly-wanted behavior for that context. (Or the behavior that produces the smallest set of matches, or whatever it is.) (3) Give a name to "context chooses" and say that's the default. The other advantage of (3) is that you can say things like zstyle ':completion:*:foo:*' prefix-needed true zstyle ':completion:*:foo:bar' prefix-needed auto whereas if the only way to get "auto" is to leave the style unset, you can't have the specific case differ from the wildcard case. But I don't know if there would ever be a need for that ... so I guess go with (2) as easier, because (3) can always be done later.