From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9738 invoked from network); 23 Jun 1999 08:59:57 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 23 Jun 1999 08:59:57 -0000 Received: (qmail 28342 invoked by alias); 23 Jun 1999 08:59:48 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6805 Received: (qmail 28335 invoked from network); 23 Jun 1999 08:59:48 -0000 From: "Andrej Borsenkow" To: "Sven Wischnowsky" , Subject: RE: PATCH: collist v2.0 Date: Wed, 23 Jun 1999 12:59:11 +0400 Message-ID: <00a401bebd56$a8f3ce20$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" 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) Importance: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: <199906230843.KAA06161@beta.informatik.hu-berlin.de> > > Hm. Autoloaded parameters are intended for modules that *define* > parameters instead of just using them. But then, complist does nothing > if `ZLS_COLO(|U)RS' isn't set. Hm. Maybe. > Thinking more about it - no. It is O.K. for ZLS_COLORS to define used colors. But I think, it complist should not depend on it being set. If you have to test parameter to decide, if run color list/menu selection - does it matter, which parameter? I prefer that completion configuration be kept in one place - and this is compconfig. what about compconf list_handler=color compconf menu_handler=select This has an advantage, that if new handler is ever added, it can easily be activated. And it can even be used to autoload modules ... /andrej