From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17044 invoked from network); 15 Mar 2002 01:17:58 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 15 Mar 2002 01:17:58 -0000 Received: (qmail 3223 invoked by alias); 15 Mar 2002 01:17:42 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 16835 Received: (qmail 3212 invoked from network); 15 Mar 2002 01:17:42 -0000 Date: Thu, 14 Mar 2002 17:17:34 -0800 (PST) From: Bart Schaefer Sender: schaefer@ns1.sodaware.com To: John Beppu cc: zsh-workers@sunsite.dk Subject: Re: completion newbie question In-Reply-To: <20020314233055.GA7934@Ax9.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 14 Mar 2002, John Beppu wrote: > I came across an idiom in _cvs that seems unnecessary. > Before every function definition, there is a guard [...] The guard is theoretically there so that a user can define his own custom overrides for each of the guarded functions and simply arrange to have his own functions autoloaded. Thus when _cvs is autoloaded, it won't override the user's existing autoloads for those functions. In practice I find that all it does is annoy me when I'm debugging, by making `unfunction _cvs; autoload -U _cvs' insufficient to reload all the related functions.