From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 268 invoked from network); 3 May 1999 10:38:13 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 3 May 1999 10:38:13 -0000 Received: (qmail 20528 invoked by alias); 3 May 1999 10:38:00 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6201 Received: (qmail 20517 invoked from network); 3 May 1999 10:37:59 -0000 Date: Mon, 3 May 1999 12:37:57 +0200 (MET DST) Message-Id: <199905031037.MAA29782@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Peter Stephenson's message of Mon, 03 May 1999 11:53:05 +0200 Subject: Re: Magic assoc arrays Peter Stephenson wrote: > Sven Wischnowsky wrote: > > Since I just wanted to play and now only want to give an example of > > what might be done, there is no doc for this. If anyone decides that > > this is worth having, I would write one. > > Maybe it could be in a module, with just some basic support in the main > shell? Then you can autoload the parameters (so there is a use for that). > Otherwise it does pollute the namespace rather. Yes, I had thought about this, too, and than forgot to mention it. There are other things I forgot to mention: - we could, of course, add some more of these: aliases, bindkeys, compctls (a problem with the first two are the different types: normal/global and widgets/string) - as you might have seen, I haven't changed anything to use this, but the example completion code could use `$commands' to get rid of the `$(whence -p ...)', it could use `$parameters' in `_parameters' and probably other things I currently can't think of. The only support needed in the core is to be able to give special scan functions. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de