From: Matt Birkholz <matt@birchwood-abbey.net>
Date: Sat, 30 Sep 2017 09:17:08 +0000 (-0700)
Subject: doc/user: PostgreSQL plugin IS available.  Use ~puck/.  Whitespace.
X-Git-Tag: mit-scheme-pucked-9.2.12~52
X-Git-Url: https://birchwood-abbey.net/git?a=commitdiff_plain;h=c71b37d7f69a9e81939f4d31af71d722f1802866;p=mit-scheme.git

doc/user: PostgreSQL plugin IS available.  Use ~puck/.  Whitespace.
---

diff --git a/doc/user-manual/user.texinfo b/doc/user-manual/user.texinfo
index 81f3a5567..03e1c2363 100644
--- a/doc/user-manual/user.texinfo
+++ b/doc/user-manual/user.texinfo
@@ -108,8 +108,9 @@ list of user-visible changes is provided in @ref{Release Notes}.
 
 @cindex Web site
 The primary distribution site for this software is
+
 @example
-@uref{http://birchwood-abbey.net/~matt/Scheme/}
+@uref{http://birchwood-abbey.net/~puck/Scheme/}
 @end example
 
 @cindex bugs, reporting
@@ -155,9 +156,11 @@ Unity or another program launcher.
 If Scheme does not seem to be available through your launcher, you
 should still be able to run it with a shell (terminal) command line.
 Simply enter the command
+
 @example
 mit-scheme-pucked --edit
 @end example
+
 @noindent
 and Scheme will load and print something like this:
 
@@ -182,9 +185,11 @@ input in the terminal.
 The version information shown above can be printed again by
 evaluating this expression.
 @findex identify-world
+
 @example
 (identify-world)
 @end example
+
 @cindex release number
 @cindex microcode, version
 @cindex runtime system, version
@@ -3833,13 +3838,15 @@ This experimental version of MIT/GNU Scheme got a new project name,
 MIT/GNU Scheme Pucked, and a new command name,
 @code{mit-scheme-pucked}, so that it can be installed alongside the
 stable release.  While it comes with an assortment of plugins and a
-strange name, the core of the system is largely unchanged.  Note that
-the core is the @emph{bleeding edge core}.  The head of the project's
-development branch on Savannah is merged in frequently.  Thus it
-includes changes proposed for the next stable release.
+strange name, the core of the system is largely unchanged.
 
 @unnumbered Proposed Changes
 
+The core of MIT/GNU Scheme Pucked is the @emph{bleeding edge core}.
+The head of the MIT/GNU Scheme project's development branch on
+Savannah is merged in frequently.  Thus it includes changes proposed
+for the next stable release of MIT/GNU Scheme.
+
 @itemize @bullet
 @item
 Most of the bindings that we would fluid bind with @code{fluid-let},
@@ -3848,12 +3855,15 @@ corresponding bindings (e.g. @code{param:parser-radix}), should be
 used instead.  @footnote{Parameters will be more easily implemented in
 SMPing (Symmetrically Multi-Processing) worlds.}  For example, rather
 than fluid binding @code{*parser-radix*} with @code{fluid-let}
+
 @example
 (fluid-let ((*parser-radix* 16))
   ...)
 @end example
+
 @noindent
 you should parameterize @code{param:parser-radix}
+
 @example
 (parameterize ((param:parser-radix 16))
   ...)
@@ -3890,14 +3900,18 @@ microcode modules and hook the Gtk screen into Edwin.  Neither change
 should be apparent to the casual user.
 
 If your code does not hack Edwin and you previously said
+
 @example
 mit-scheme --load my-code
 @end example
+
 @noindent
 you should be able to say
+
 @example
 mit-scheme-pucked --load my-code
 @end example
+
 @noindent
 and be no worse off.
 
@@ -3930,11 +3944,6 @@ procedures are moot).  Thus something like
 @code{(gdbm-available?)}  should be replaced with
 @code{(plugin-available? "gdbm")}.
 
-@item
-The @code{(runtime postgresql)} package was removed but has not yet
-been replaced with a corresponding plugin.  If you were using it, let
-Puck know.
-
 @item
 The @code{(runtime crypto)} and @code{(runtime blowfish)} packages are
 provided but deprecated.  Their bindings are unassigned until
@@ -3967,9 +3976,11 @@ available through an icon (a lambda holding a fountain pen) in a
 The installation process includes HTML documentation by default.  In
 the right place these files are available in your web browser, whether
 online or offline, using a file URL like the following Ubuntu locator.
+
 @example
 @url{file:///usr/share/doc/mit-scheme-pucked/html/index.html}
 @end example
+
 HTML documentation for installed plugins is found in the same location.
 
 @item
@@ -3988,7 +3999,7 @@ text using Pango.
 MIT/GNU Scheme Pucked and its plugins are now available as packages
 for recent versions of Ubuntu on Intel@registeredsymbol{}64 and IA-32
 architecture machines.  If
-@uref{http://birchwood-abbey.net/~matt/Scheme/} has links to packages
+@uref{http://birchwood-abbey.net/~puck/Scheme/} has links to packages
 for your Ubuntu, you can use your Ubuntu package manager to add,
 remove and update Scheme and its plugins.  @xref{Ubuntu Installation}.
 
@@ -4014,21 +4025,26 @@ just like other packages.
 
 You should begin by installing the GPG key used to sign the packages.
 It is available from this web page:
+
 @example
 @url{https://savannah.gnu.org/users/mhb}
 @end example
+
 Click the ``Download GPG Key'' link on that page and save the
 @file{mhb-key.gpg} file.  You might install it with this command:
+
 @example
 sudo apt-key add ~/Downloads/mhb-key.gpg
 @end example
 
 Next add the repository to your list of package sources.
-On Ubuntu 16.10 (Yakkety Yak) you would use this command:
+On Ubuntu 17.04 (Zesty Zapus) you would use this command:
+
 @example
 sudo add-apt-repository \
         -s "deb http://birchwood-abbey.net/ubuntu/ birchwood yakkety"
 @end example
+
 or by editing files in @file{/etc/apt/}.
 
 Finally, use your package manager to update its list of available
@@ -4039,6 +4055,7 @@ plugins depend on it.  You might choose the
 Scheme and Edwin and makes Scheme a graphical X11 application like the
 original MIT/GNU Scheme.  You could do this with Apt by entering the
 following commands.
+
 @example
 sudo apt-get update
 sudo apt-get install mit-scheme-pucked-x11-screen
@@ -4046,9 +4063,11 @@ sudo apt-get install mit-scheme-pucked-x11-screen
 
 You can also download the package files and install them by hand.  Links to
 the available package files are listed on the project home page.
+
 @example
-@uref{http://birchwood-abbey.net/~matt/Scheme/}
+@uref{http://birchwood-abbey.net/~puck/Scheme/}
 @end example
+
 You will need to know your Ubuntu version (e.g. 16.10) and Debian
 machine architecture (e.g. amd64), then click on the corresponding
 link.  You will need to do this for your chosen plugin, all of the
@@ -4066,15 +4085,20 @@ you will need the corresponding @file{.changes} files.  Each contains
 checksums for the package files and is signed.  If you saved the GPG
 key in @file{~/Downloads/mhb-key.gpg}, you can add it to your keyring
 like this:
+
 @example
 gpg --import ~/Downloads/mhb-key.gpg
 @end example
+
 Then verify the signature on the @file{.changes} file like this:
+
 @example
 gpg --verify ~/Downloads/mit-scheme-pucked_9.2.7-1_amd64.changes
 @end example
+
 Finally compare the checksum in the @file{.changes} file with one
 computed from your downloaded file.
+
 @example
 grep mit-scheme-pucked_9.2.7-1_amd64.deb \
      mit-scheme-pucked_9.2.7-1_amd64.changes
@@ -4126,22 +4150,29 @@ binaries for the core system.  Save the file, which should be named
 something like @file{mit-scheme-pucked-9.2.7-i386.tar.gz}.
 
 Compile the Scheme interpreter using the following steps:
+
 @enumerate
 @item
 Unpack the archive to create your build directory, e.g.@:
 @file{mit-scheme-pucked-9.2.7}.  For example,
+
 @example
 tar xzf mit-scheme-pucked-9.2.7-i386.tar.gz
 @end example
+
 will create a new directory @file{mit-scheme-pucked-9.2.7}.
+
 @item
 Move into the @file{src} subdirectory of the new directory:
+
 @example
 cd mit-scheme-pucked-9.2.7/src
 @end example
+
 @item
 @anchor{Build Configuration}
 Configure the software:
+
 @example
 ./configure
 @end example
@@ -4151,6 +4182,7 @@ the subdirectories @file{bin} and @file{lib}.  If you want it
 installed somewhere else, for example @file{/opt}, pass the
 @option{--prefix} option to the configure script, as in the
 command line below.
+
 @example
 ./configure --prefix=/opt
 @end example
@@ -4203,6 +4235,7 @@ automake (and autoconf).  Thus make targets like @code{dist} and
 
 Installation is per the GNU custom, not unlike the core
 installation.  For the Gtk+ plugin:
+
 @example
 tar xzf mit-scheme-pucked-gtk-0.5-i386.tar.gz
 cd mit-scheme-pucked-gtk-0.5
@@ -4219,11 +4252,14 @@ is not writable by you, super-user privileges may be required.
 You can put a writable directory at the front of your host Scheme's
 library path by setting the @code{MITSCHEME_LIBRARY_PATH} environment
 variable
+
 @example
 export MITSCHEME_LIBRARY_PATH=~/pucked:/opt/lib/mit-scheme-pucked
 @end example
+
 @noindent
 or including the @code{--library} option on the command line.
+
 @example
 mit-scheme-pucked --library ~/pucked:/opt/lib/mit-scheme-pucked
 @end example