0.8.13.36: NO-WORD-BYTES?

[sbcl.git] / doc / manual / beyond-ansi.texinfo

diff --git a/doc/manual/beyond-ansi.texinfo b/doc/manual/beyond-ansi.texinfo
index a8c8a28..03a5082 100644 (file)
--- a/doc/manual/beyond-ansi.texinfo
+++ b/doc/manual/beyond-ansi.texinfo
@@ -319,6 +319,13 @@ following way:
 @include fun-common-lisp-require.texinfo
 @include var-sb-ext-star-module-provider-functions-star.texinfo
 
 @include fun-common-lisp-require.texinfo
 @include var-sb-ext-star-module-provider-functions-star.texinfo
 

+Although SBCL does not provide a resident editor, the @code{ed}
+function can be customized to hook into user-provided editing
+mechanisms as follows:
+
+@include fun-common-lisp-ed.texinfo
+@include var-sb-ext-star-ed-functions-star.texinfo
+

 @node  Tools To Help Developers
 @comment  node-name,  next,  previous,  up
 @subsection Tools To Help Developers
 @node  Tools To Help Developers
 @comment  node-name,  next,  previous,  up
 @subsection Tools To Help Developers

@@ -340,12 +347,13 @@ the @code{inspect} prompt.
 SBCL has the ability to save its state as a file for later
 execution. This functionality is important for its bootstrapping
 process, and is also provided as an extension to the user.  Note that
 SBCL has the ability to save its state as a file for later
 execution. This functionality is important for its bootstrapping
 process, and is also provided as an extension to the user.  Note that

-foreign libraries loaded via @code{load-1-foreign} don't survive this
-process; a core should not be saved in this case.
+foreign libraries loaded via @code{load-shared-object} don't survive
+this process; a core should not be saved in this case.

 
 @emph{FIXME: what should be done for foreign libraries?}
 
 
 @emph{FIXME: what should be done for foreign libraries?}
 

-@emph{FIXME: document load-1-foreign somewhere}
+@emph{FIXME: document load-shared-object somewhere - it's in
+ffi.texinfo?}

 
 @include fun-sb-ext-save-lisp-and-die.texinfo
 
 
 @include fun-sb-ext-save-lisp-and-die.texinfo