From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3014 invoked from network); 19 Feb 1999 11:48:37 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 19 Feb 1999 11:48:37 -0000 Received: (qmail 14534 invoked by alias); 19 Feb 1999 11:47:54 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5428 Received: (qmail 14517 invoked from network); 19 Feb 1999 11:47:43 -0000 Date: Fri, 19 Feb 1999 12:46:53 +0100 (MET) Message-Id: <199902191146.MAA10937@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Peter Stephenson's message of Fri, 19 Feb 1999 11:27:03 +0100 Subject: Re: PATCH: 3.1.5-pws-8: using pattern completions Peter Stephenson wrote: > I wrote: > > Now, can anyone tell me how to avoid getting a default completion list for > > the pattern completions as well? This is rather crucial since I'm trying > > to get all zf* files to use zftp completion, and I don't want a side dish > > of local filenames with every order. > > Just thinking: suppose we had a convention where if $COMPSKIP was non-empty > at any stage, the driver functions (principally __main_complete and > __normal) would stop generating matches at that point, unset COMPSKIP, and > return? That would act like -tn with ordinary compctl's. Yes, using a parameter for this was what I thought about, too. > Btw, would it be better to rename AUTODUMP to COMPAUTODUMP to have a > consistent prefix? I'd like to remove that parameter anyway: let `init' accept an options (-d or so) to enable auto-dumping. It's used only in `init' anyway. And while I'm at it: I'd like to make `dump' write into a file automatically (let it use COMPDUMP, too, with the usual default), so that it is even easier to make dumps in-between (once we have changed the example code so that this is possible). Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de