From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4510 invoked from network); 10 Aug 2000 07:09:24 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 10 Aug 2000 07:09:24 -0000 Received: (qmail 21065 invoked by alias); 10 Aug 2000 07:09:08 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12580 Received: (qmail 21058 invoked from network); 10 Aug 2000 07:09:07 -0000 Date: Thu, 10 Aug 2000 09:08:51 +0200 (MET DST) Message-Id: <200008100708.JAA08916@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Oliver Kiddle's message of Wed, 09 Aug 2000 21:10:51 +0100 Subject: Re: PATCH: New _read and selective parameter completion Oliver Kiddle wrote: > This adds an _arguments based completion function for read. I don't think > we have too many builtins left where conversion to use _arguments would > still be useful. Any requests? > > I thought about modifying _vars to insert the '[' for arrays and > associations but _parameters would first need to be given an option to > make it only complete specific types of parameter. Would anyone object > to my adding this? I was thinking of a -g option (analogous to the -g > option of _files) where the pattern specified would be augmented with > ~*local* and used to match the values in the $parameters association. > > I mentioned this vaguely before in 11284 and Sven had some good ideas > in his reply (11293). The focus there is more towards having the > patterns configurable via a style similar to the file-patterns tag but > my suggested option would I think be a useful first step. Yes. The other stuff can be added later. I'd be happy if we were able to use _parameters in all places where parameters are completed (e.g. in _arrays), just as we use _files now. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de