From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10897 invoked from network); 6 Jan 2000 09:50:45 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 6 Jan 2000 09:50:45 -0000 Received: (qmail 19533 invoked by alias); 6 Jan 2000 09:50:40 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9239 Received: (qmail 19526 invoked from network); 6 Jan 2000 09:50:39 -0000 Date: Thu, 6 Jan 2000 10:50:38 +0100 (MET) Message-Id: <200001060950.KAA17645@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Andrej Borsenkow"'s message of Thu, 6 Jan 2000 10:38:17 +0300 Subject: Re: zmodload in static zsh Andrej Borsenkow wrote: > I vaguelly remember, Zefram changed zmodload so, that it works the same way in > dynamic and static builds of zsh. > > Is it possible to compile in all modules in static versions and use zmodload to > enable/disable them at runtime? In this case, xmods.conf would list modules > enabled by default. > > Or is it already the case? Almost. xmods.conf lists the modules the shell `knows' about. I.e. the modules that will automatically be loaded or, if linked-in, enabled when one of its auto-somethings is used. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de