From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17605 invoked from network); 11 Apr 2002 19:45:57 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 11 Apr 2002 19:45:57 -0000 Received: (qmail 4778 invoked by alias); 11 Apr 2002 19:45:52 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 16964 Received: (qmail 4764 invoked from network); 11 Apr 2002 19:45:50 -0000 Date: Thu, 11 Apr 2002 12:46:34 -0700 From: John Beppu To: Zsh Workers Subject: Re: Rough Draft of Article on Writing Completion Functions Message-ID: <20020411194634.GA27390@Ax9.org> References: <20020404234932.GA27875@Ax9.org> <7906.1018000673@csr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7906.1018000673@csr.com> User-Agent: Mutt/1.3.27i [ date ] 2002/04/05 | Friday | 10:57 AM [ author ] Peter Stephenson > I deliberately didn't write a whole real-world completion function > because there are already so many to look at, I think you should have done it, anyway. I'll explain why in a second. > > The great tragedy of Zsh is that they actually made it very easy to > > write completion functions, but you'd never know it by just > > reading the documentation. > > Hmm... how much simpler than > > _foo() { compadd Yan Tan Tethera; } > compdef _foo foo > > do I need to get? This is the sort of hint I need from the puzzled. Beginners don't need "simple". They need "practical". Would you tell some chump off the street: This is how to jab; This is a hook; This is an uppercut; Now go fight Mike Tyson. Clearly, this guy is going to be unprepared for the task at hand. That's why a long practical example that explains the task of writing a completion function from start to finish would have been helpful. > I suggest you mention that you need zsh 4.0.x as a matter of priority, > regardless of space limitations, or some people are going to get > confused OK.