From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8326 invoked from network); 29 Jun 1999 12:03:26 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 29 Jun 1999 12:03:26 -0000 Received: (qmail 19973 invoked by alias); 29 Jun 1999 12:03:18 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6918 Received: (qmail 19966 invoked from network); 29 Jun 1999 12:03:17 -0000 Date: Tue, 29 Jun 1999 14:03:16 +0200 (MET DST) Message-Id: <199906291203.OAA23049@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Andrej Borsenkow"'s message of Tue, 29 Jun 1999 15:47:25 +0400 Subject: Re: compinit/compdef useful outside of completion? Andrej Borsenkow wrote: > Don't you think, that these can be used not only with completion widgets? I > actually like the idea, when I just need to drop a file in defined place and it > will automatically be used next time I start shell. No more .zshrc editing etc. > > What I mean, does it make sense to extend compinit/compdef to handle "normal" > user defined widgets as well ('course, the names will probably be too misleading > ...). E.g. 'compdef -w widget function' to define normal widget. You could even > automatically bind it to key sequence with additional parameter ... say "-k > ^Xn"? > And start function with '#compdef -w ' I've been thinking about this, too. Some kind of autoauto-functions with arguments describing the tags to expect and what to do with them. Or some external configuration and then cal autoauto or whatever. (Heck, haven't I mentioned that yet? I thought I had, but maybe I've been only thinking too much about it.) This is even more interesting if we once get into heavy widget-hacking. What I'm currently thinking about is how we could generalise the dumping code and integrate it with a generic autoauto function. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de