From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19259 invoked by alias); 5 Feb 2014 17:46:42 -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: 32354 Received: (qmail 17632 invoked from network); 5 Feb 2014 17:46:36 -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=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, SPF_HELO_PASS autolearn=ham version=3.3.2 X-AuditID: cbfec7f4-b7f796d000005a13-53-52f2769f10cc Date: Wed, 05 Feb 2014 17:36:29 +0000 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: Tests of interrupting completion, and completion_nostat_dirs Message-id: <20140205173629.47e22088@pwslap01u.europe.root.pri> In-reply-to: <140205091501.ZM22649@torch.brasslantern.com> References: <140122000435.ZM1516@torch.brasslantern.com> <140123171659.ZM19422@torch.brasslantern.com> <87iot91lp8.fsf@lwm.klanderman.net> <140125124934.ZM23767@torch.brasslantern.com> <87eh3q3g63.fsf@lwm.klanderman.net> <140129181206.ZM22813@torch.brasslantern.com> <20140130093057.6e04fa53@pwslap01u.europe.root.pri> <140130082206.ZM23682@torch.brasslantern.com> <874n4g1blj.fsf@lwm.klanderman.net> <140204212859.ZM21837@torch.brasslantern.com> <874n4dpss0.fsf@lwm.klanderman.net> <20140205142303.400fe22b@pwslap01u.europe.root.pri> <140205091501.ZM22649@torch.brasslantern.com> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplluLIzCtJLcpLzFFi42I5/e/4Nd35ZZ+CDOZv57Y42PyQyYHRY9XB D0wBjFFcNimpOZllqUX6dglcGVdPv2IqOMNZ8ffTQrYGxuvsXYycHBICJhJTz+xmhLDFJC7c W8/WxcjFISSwlFFi2ZnprBDOciaJuZOesYJUsQioShz68JoFxGYTMJSYumk2WLeIgLjE2bXn geIcHMICnhJz5hSAhHkF7CXmPLoA1sopYCXR/fU/O8TMN6wScxf9B7uCX0Bf4urfT0wQV9hL zLxyhhGiWVDix+R7YLuYBbQkNm9rYoWw5SU2r3nLPIFRYBaSsllIymYhKVvAyLyKUTS1NLmg OCk911CvODG3uDQvXS85P3cTIyQIv+xgXHzM6hCjAAejEg9vh+jHICHWxLLiytxDjBIczEoi vLszPgUJ8aYkVlalFuXHF5XmpBYfYmTi4JRqYGxYEvP3sfYShzsbvzzhO3TDJ1pvu1idpaV5 7vvbH3Uspk7V7/LsyrTqOFqvKfFkcQz3ZOvmNa8uLlxl8Nw/aIJAUqFmb8nU5Lmcf9XnsG+S MnhfdWXzsZSL0V2vzPfY/r+wda1a8yml3PsP2y/OFOZknXZz/kKGG13/p3gyJf/zCnh6Jju+ vViJpTgj0VCLuag4EQDj43a0IAIAAA== On Wed, 05 Feb 2014 09:15:01 -0800 Bart Schaefer wrote: > On Feb 5, 2:23pm, Peter Stephenson wrote: > } > } Looks like the right answer is to add the parameter within > } complete.c. > > And declare it as a feature to solve Greg's problem above? If it's only > a special parameter when completion is actually in progress, it can't be > tested from a startup file. Hmmm... parameter features are handled automatically, so the parameter would be added permanently. However, there is the option of adding non-standard (looks like I called them "abstract") features that aren't handled automatically by the feature mechanism, so we could add that (and make it do nothing when enabled or disabled). Really, this is asking for something a bit more lightweight within the feature mechanism, i.e. a set of flags that you can query but not turn on or off. But having something in the main shell to test for a completion feature doesn't sound the right solution, so we should probably do something like this. (The other way would be to use the zstyle -e option to execute some code when the style is requested, which would ensure all the requirements are satisfied.) pws