From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26266 invoked from network); 30 Apr 1999 18:42:50 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 30 Apr 1999 18:42:50 -0000 Received: (qmail 26952 invoked by alias); 30 Apr 1999 18:42:41 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6178 Received: (qmail 26944 invoked from network); 30 Apr 1999 18:42:26 -0000 From: "Bart Schaefer" Message-Id: <990430114057.ZM18502@candle.brasslantern.com> Date: Fri, 30 Apr 1999 11:40:57 -0700 In-Reply-To: <199904300707.JAA21821@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "Re: completion in vared" (Apr 30, 9:07am) References: <199904300707.JAA21821@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (4.0b.820 20aug96) To: zsh-workers@sunsite.auc.dk Subject: Re: completion in vared MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 30, 9:07am, Sven Wischnowsky wrote: } Subject: Re: completion in vared } } } Bart Schaefer wrote: } > By the way, if we're reasonably confident that we've now identified all } > the compctl-isms that it's useful to put into compadd/gen/etc., I think } > we should seriously look at rewriting the option parsing for those new } > commands to abandon the compctl syntax. } } I /think/ you are referring to an old suggestion to just give a } builtin that gets the matches to be added directly (that would be } compadd) and let the user generate these matches/words through shell } code. No, I'm mostly thinking of the compctl options that have poor mnemonics, and particularly of -J and -V (which are begging for a bracketed-looking syntax). There is some advantage to having the options of the new commands be the same as those of compctl, but I'm not sure if it's enough to outweigh the opportunity to clean it up a bit. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com