Punt mention of nonexistent microcode modules and conflicting bindings.
Punt import-blowfish and import-gdbm2. Fix stale references to GDBM2.
The Blowfish option.
-This plugin creates a (blowfish) package, a drop-in replacement for
-the microcode module based (runtime blowfish) package. It is built in
-the customary GNU way:
+This plugin creates a (blowfish) package. It is built in the
+customary GNU way:
./configure [--with-openssl=directory]...
make all check install
To use:
(load-option 'blowfish)
- (import-blowfish)
-
-Import-blowfish will modify the REPL's current environment by adding
-bindings linked to the plugin's exports. They are not exported to the
-global environment because they would conflict with the exports from
-(runtime blowfish).
To import into a CREF package set, add this to your .pkg file:
+The EDWIN option.
+
+This option extends Scheme with a source code (text) editor. After
+loading this option, a global procedure named `edit' should be
+available.
+
+For more information see the accompanying user / reference manual.
+
+
Notes on the Edwin sources:
If you want to add a new file to the source tree, you need to
-The GDBM2 option.
+The GDBM option.
-This plugin creates a (gdbm) package, a drop-in replacement for the
-microcode module based (runtime gdbm) package. It is built in the
-customary GNU way:
+This plugin creates a (gdbm) package. It is built in the customary
+GNU way:
./configure ...
make all check install
To use:
- (load-option 'gdbm2)
- (import-gdbm2)
-
-Import-gdbm2 will modify the REPL's current environment by adding
-bindings linked to the plugin's exports. They are not exported to the
-global environment because they would conflict with the exports from
-(runtime gdbm).
+ (load-option 'gdbm)
To import into a CREF package set, add this to your .pkg file:
+The IMAIL option.
+
+This option extends Edwin with an IMAP email reader. After loading
+this option, an Edwin command named `imail' should be available.
+
+For more information see the accompanying user / reference manual.
+
+
Notes on the Edwin sources:
If you want to add a new file to the source tree, you need to
The Mcrypt option.
-This plugin creates an (mcrypt) package, a drop-in replacement for the
-microcode module based mcrypt-* procedures in the (runtime crypto)
-package. It is built in the customary GNU way:
+This plugin creates an (mcrypt) package. It is built in the customary
+GNU way:
./configure ...
make all check install
The MD5 option.
-This plugin creates an (md5) package, a drop-in replacement for the
-microcode module based md5-* procedures in the (runtime crypto)
-package. It is built in the customary GNU way:
+This plugin creates an (md5) package. It is built in the customary
+GNU way:
./configure [--with-openssl=directory]...
make all check install
The Mhash option.
-This plugin creates an (mhash) package, a drop-in replacement for the
-microcode module based mhash-* procedures in the (runtime crypto)
-package. It is built in the customary GNU way:
+This plugin creates an (mhash) package. It is built in the customary
+GNU way:
./configure ...
make all check install
The X11-SCREEN option.
This plugin creates an (edwin screen x11-screen) package that
-registers an Edwin display type named X11, an exact replacement for
-the microcode module based X screen type. The plugin is built in the
+registers an Edwin display type named X11. The plugin is built in the
customary GNU way:
./configure ...
Loading this plugin re-assigns bindings in (edwin) and (edwin
x-commands); any existing Edwin screens will stop working. You must
load this option before starting Edwin. If the DISPLAY environment
-variable is set, Edwin will create X11 screens.
+variable is set, Edwin will then create X11 screens.
The X11 option.
This plugin creates an (x11) package that registers a graphics device
-type named X11, an exact replacement for the microcode module based X
-graphics device type. The plugin is built in the customary GNU way:
+type named X11. The plugin is built in the customary GNU way:
./configure ...
make all check install