Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Monolithic zsh with an attitude
- X-seq: zsh-workers 16188
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Raúl Núñez de Arenas Coronado <dervishd@xxxxxxxxxxxx>, Zsh <zsh-workers@xxxxxxxxxx>
- Subject: Re: Monolithic zsh with an attitude
- Date: Sun, 28 Oct 2001 21:45:18 +0000
- In-reply-to: <E15xwYV-0001eZ-00@DervishD>Comments: In reply to Raúl Núñez de Arenas Coronado <dervishd@xxxxxxxxxxxx> "Monolithic zsh with an attitude" (Oct 28, 9:29pm)
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <E15xwYV-0001eZ-00@DervishD>
On Oct 28, 9:29pm, Raúl Núñez de Arenas Coronado wrote:
}
} [...] 'configure' doesn't provide a way of choosing whether the
} modules must be included in the monolithic zsh (that's obvious too,
} and desirable).
If you read the INSTALL file, you'll find the answers you seek:
The key to the module system is the file config.modules, created in
the configuration process. In the normal case that dynamic loading is
available, all modules relevant to your configuration will be compiled
and installed as separate files, so unless you want the modules to be
loaded by default you don't need to do anything. For a non-dynamic zsh,
the default is to compile the complete, compctl, zle, computil, complist,
sched, parameter, zleparameter and rlimits modules into the shell, and
you will need to edit config.modules to make any other modules available.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author