From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17094 invoked from network); 2 Feb 2000 16:52:30 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 Feb 2000 16:52:30 -0000 Received: (qmail 21154 invoked by alias); 2 Feb 2000 16:52:26 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9536 Received: (qmail 21147 invoked from network); 2 Feb 2000 16:52:26 -0000 To: Sven Wischnowsky Cc: zsh-workers@sunsite.auc.dk Subject: Re: _call (was: Re: PATCH: _diff (new), _prcs (upgrade)) References: <200002021421.PAA11232@beta.informatik.hu-berlin.de> X-Attribution: adl From: Alexandre Duret-Lutz Date: 02 Feb 2000 17:51:02 +0100 In-Reply-To: Sven Wischnowsky's message of "Wed, 2 Feb 2000 15:21:17 +0100 (MET)" Message-ID: User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii >>> "Sven" == Sven Wischnowsky writes: [...] Sven> So, maybe we should just make Sven> _call get the suggested command line and let users override them Sven> completely or leave them alone. I would then make _call take a tag as Sven> its first argument which is used to look up the style `command' This looks easy to use. [...] Sven> The only problem is that -- in cases like the _diff -- the users would Sven> have to know what the command has to do, but as long as we keep tags Sven> and styles documented... Could there be a way to make the completion functions autodescribe themselve? (i.e. print styles and tags used by the function, as well as other info worth to know, in some standard way). Perhaps it can be made by using some special comments in the completions functions and having a simple shell function that take a command as argument, that find the completion function associated and format out these comments. [...] -- Alexandre Duret-Lutz