From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22702 invoked from network); 26 Jul 2000 16:24:57 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 26 Jul 2000 16:24:57 -0000 Received: (qmail 17546 invoked by alias); 26 Jul 2000 16:24:35 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 3340 Received: (qmail 17537 invoked from network); 26 Jul 2000 16:24:30 -0000 Date: Wed, 26 Jul 2000 18:24:19 +0200 From: Matthias Kopfermann To: Sven Wischnowsky Cc: zsh-users@sunsite.auc.dk Subject: Re: how can one let completion work *inside* zsh scripts? Message-ID: <20000726182419.A19075@linux-ws.kg-hittfeld.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from wischnow@informatik.hu-berlin.de on Wed, Jul 26, 2000 at 02:00:11PM +0200 On Wed, Jul 26, 2000 at 02:00:11PM +0200, Sven Wischnowsky wrote: > > Then... do you really need a *script*? Or would a function do? no, as long as it is interactive i don't care. But i was not thinking of filename completion, more of the ability to let users easily choose options whatever. Another way is select of course but i always wanted to know how to be able to do it with little zsh scripts, too. >. If you need something else > than filename completion, the `offical' way to do that is to (locally) > define the parameter compcontex and set it to the name of the > completion context that should be used for completion. this was new to me. Thanx for explaining! Matthias