From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12790 invoked from network); 11 Nov 1999 11:54:06 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 11 Nov 1999 11:54:06 -0000 Received: (qmail 5531 invoked by alias); 11 Nov 1999 11:53:47 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8626 Received: (qmail 5524 invoked from network); 11 Nov 1999 11:53:47 -0000 Date: Thu, 11 Nov 1999 12:53:45 +0100 (MET) Message-Id: <199911111153.MAA28904@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Sven Wischnowsky's message of Thu, 11 Nov 1999 11:24:31 +0100 (MET) Subject: Re: New configuration -- should we... I forgot to mention: One of the things I want all this new configu stuff for is to be able to control more detailed what matches will be generated form the *outside* of the (real) completion system. I.e. functions that use the normal completion context but restrict/change what would normally be added. In my previous suggestions I had the `override_tags' assoc which was so ugly that I already removed it in my private version, in the hope that I could find something better. When we the function approach this would be extremly simple. `_tags' checks if a parameter with a certain name is set and non-empty. If so, it uses that value as the name of the config function to call. Functions that which to override the normal settings would then just use their own config function, basta. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de