From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24870 invoked from network); 3 Jul 2001 17:19:36 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 3 Jul 2001 17:19:36 -0000 Received: (qmail 22251 invoked by alias); 3 Jul 2001 17:18:36 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15240 Received: (qmail 22223 invoked from network); 3 Jul 2001 17:18:35 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) From: "Andrej Borsenkow" To: Subject: RE: PATCH: zsh/pcre module Date: Tue, 3 Jul 2001 21:19:26 +0400 Message-ID: <005f01c103e4$4fa1b8b0$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20010703125955.A5441@dman.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 > > > How easy is it to package up modules separately in such a way that they > > could be built and installed without needing to be unpacked over the zsh > > source and compiled with it. Ideally, we would have a set of include > > files which was all anyone needed to build a separate zsh module. > > Also, there would need to be a mechanism for dynamically scanning for > autobins/autoparams/&c. One could scan for module dependencies at the > same time. > > That is exactly what I have suggested - scan *.zmd files on startup and register all auto*s found there. -andrej