Loading a SXEmacs Emodules is usually simply a matter of…
Emodules can also be loaded interactively with…
#’load-module supports completion, making it a bit easier for the user.
The default search path for Emodules (also known as module-load-path) is…
~/.sxemacs/$machinetriplet/modules $prefix/lib/sxemacs/$machinetriplet/site-modules $prefix/lib/sxemacs-$version/$machinetriplet/modules
Searching recurses down one level below these directories. The module-load-path is also part of the standard load-path. This means that if an emodule shares the same feature symbol name as a elisp library in the load-path, that one that is loaded from a #’require call will be the one that is higher up in the load-path.
It is possible to set the module-load-path at SXEmacs configure time using the --with-module-path=PATH configure option. But you normally would not need to do this, as SXEmacs’ build chain is smart enough to set sane defaults.
Locating where a particular emodule is installed on disc can be done with the function, #’locate-module.
To see which emodules are loaded in the current SXEmacs session, use #’list-modules. It returns a list of emodule names (strings), or if called interactively, it displays the list of emodules in the echo area. The names are the emodules’ internal.
(list-modules) ⇒ ("cl" "cl-loop" "ase" "ase_set")