From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25845 invoked from network); 14 Apr 1999 12:24:36 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 14 Apr 1999 12:24:36 -0000 Received: (qmail 4665 invoked by alias); 14 Apr 1999 12:24:17 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6034 Received: (qmail 4658 invoked from network); 14 Apr 1999 12:24:16 -0000 From: "Andrej Borsenkow" To: "ZSH workers mailing list" Subject: compinit as function? Date: Wed, 14 Apr 1999 16:23:35 +0400 Message-ID: <009201be8671$9e448670$21c9ca95@mowp.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Is there any real reason, why compinit cannot be a function? The only problem as far as I can see is, that it defines several global AA's - and current typeset's will make them local. One workaround is to use : ${(AA)hash:=} (it is ugly, but it works) Another possibility is to add the global flag to typeset: typeset -g. Can it be useful in other cases? Having compinit as function will allow to simply drop the whole stuff in auoloaded fpath - and don't worry about path to compinit anymore. Of course, then some other standard path to dump file is needed. /andrej