Here are a set of patches for minor spelling or grammar errors that
I found in the Geiser documentation (for example, replacing "i'm" with
"I'm")
after running 'ispell' on them and reading the Info file generated from
the
sources. The sources were retrieved from the Geiser 'git' repository.
Also, I could not find any information in the Geiser Info documentation
on
where to send reports about problems, patches, or questions.
diff --git a/doc/cheat.texi b/doc/cheat.texi
index 35d57de..f72f00c 100644
--- a/doc/cheat.texi
+++ b/doc/cheat.texi
@@ -84,10 +84,10 @@
@tab geiser-autodoc-mode
@tab Toggle autodoc mode
@item @tab @tab
-...@item C-c<
+...@item C-c <
@tab geiser-xref-callers
@tab Show callers of procedure at point
-...@item C-c>
+...@item C-c >
@tab geiser-xref-callees
@tab Show callees of procedure at point
@item @tab @tab
@@ -160,7 +160,7 @@
@tab forward-button
@tab Next link
@item S-TAB, p
-...@tab backwards-button
+...@tab backward-button
@tab Previous link
@item N
@tab geiser-doc-next-section @tab Next section
diff --git a/doc/install.texi b/doc/install.texi
index 6f3ee07..955e8ff 100644
--- a/doc/install.texi
+++ b/doc/install.texi
@@ -13,8 +13,8 @@
@cindex supported versions
@cindex versions supported
If Geiser came with any guarantees, you'd break all of them by not using
-GNU Emacs 23.2 (or better: i regularly use it with a recent Emacs
-snapshot) and at least one of the supported schemes, namely:
+GNU Emacs 23.2 (or better: I regularly use it with a recent Emacs
+snapshot) and at least one of the supported Schemes, namely:
@itemize @bullet
@item
@@ -65,7 +65,7 @@ code. I'll follow you into its directory and the next section.
Geiser is ready to be used out of the box without much more ado. For the
sake of concreteness, let's assume you put its source in the directory
@file{~/lisp/geiser}. All you need to do is to add the following
-line to your Emacs initialisation file (be it @file{~/.emacs} or any of
+line to your Emacs initialization file (be it @file{~/.emacs} or any of
its moral equivalents):
@example
(load-file "~/lisp/geiser/elisp/geiser.el")
@@ -101,7 +101,7 @@ $ make all
@end example
Now you have two options: loading the byte-compiled Geiser from the
@file{elisp} subdirectory, or installing it system-wide. To load the
-bytecode from here, add this line to your initialisation file:
+byte-code from here, add this line to your initialization file:
@example
(load "~/lisp/geiser/build/elisp/geiser-load")
@end example
@@ -117,7 +117,7 @@ $ sudo make install
With the above spell, Geiser will be compiled and installed in a safe
place inside Emacs load path. To load it into Emacs you'll need,
@i{instead} of the @code{load-file} form above, the following line in
-your initialisation file:
+your initialization file:
@example
(require 'geiser-install)
@end example
@@ -157,7 +157,7 @@ this screencast}.
You can still use the many goodies provided by Neil van Dyke's
@code{quack-mode}, since most of them are not (yet) available in Geiser.
The only caveat might be a conflict between Quack's and Geiser's default
-key bindings, which i'm sure you'll manage to tackle just fine. It's
+key bindings, which I'm sure you'll manage to tackle just fine. It's
also probably a good idea to require @code{quack} @i{after} loading
@file{geiser.el} (or requiring a compiled version).
@end itemize
diff --git a/doc/intro.texi b/doc/intro.texi
index f26fa7b..1525c2d 100644
--- a/doc/intro.texi
+++ b/doc/intro.texi
@@ -28,8 +28,8 @@ bulk of the code.
Scheme-Elisp interface makes some assumptions about the capabilities and
interaction mode of the corresponding REPL. In particular, Geiser
expects the latter to support namespaces in the form of a module system,
-and to provide a well defined way to establish the REPL's current
-namespace (or module), as well as the current's file module (or
+and to provide a well-defined way to establish the REPL's current
+namespace (or module), as well as the current file's module (or
namespace). Thus, all evaluations performed by Geiser either in the
REPL or in a source code buffer happen in the context of the current
namespace. Every time you switch to a different file, you're switching
@@ -37,20 +37,20 @@ namespaces automatically; at the REPL, you must request the switch
explicitly (usually just using means provided by the Scheme
implementation itself).
-If your favourite scheme supports the above modus operandi, it has all
+If your favorite Scheme supports the above modus operandi, it has all
that's needed for a bare-bones Geiser mode. But Geiser can, and will,
-use any metadata available: procedure arities and argument lists to
+use any meta-data available: procedure arities and argument lists to
display interactive help, documentation strings, location information to
jump to definitions, export lists to provide completion, and so on and
so forth. Although this is not an all-or-none proposition (Geiser can
-operate with just part of that functionality available), i've
-concentrated initially in supporting those Schemes with the richest (to
+operate with just part of that functionality available), I've
+initially concentrated on supporting those Schemes with the richest (to
my knowledge) introspection capabilities, namely, Guile and Racket.
@node Showing off, , Modus operandi, Introduction
@section Showing off
@cindex swanking
-When working with a fully conniving Scheme, Geiser can offer the
+When working with a fully conforming Scheme, Geiser can offer the
following functionality:
@itemize @bullet
@@ -82,8 +82,8 @@ debugging) and error navigation.
Support for multiple, simultaneous REPLs.
@end itemize
-In the following pages, i'll try to explain what these features
-actually are (i'm just swanking here), and how to use them for your
+In the following pages, I'll try to explain what these features
+actually are (I'm just swanking here), and how to use them for your
profit. But, before that, let's see how to install Geiser.
@c Local Variables:
diff --git a/doc/parens.texi b/doc/parens.texi
index 6bd5e5f..2c9e59d 100644
--- a/doc/parens.texi
+++ b/doc/parens.texi
@@ -6,7 +6,7 @@ hacking environment. Well, perhaps a bit more than a half; but, at any
rate, one surely needs also a pleasant way of editing source code. Don't
pay attention to naysayers: Emacs comes with an excellent editor
included for about any language on Earth, and just the best one when
-that language is sexpy (specially if you use @ref{paredit,,Paredit}).
+that language is sexpy (especially if you use @ref{paredit,,Paredit}).
Geiser's support for writing Scheme code adds to Emacs'
@code{scheme-mode}, rather than supplanting it; and it does so by means
of a minor mode (unimaginatively dubbed @code{geiser-mode}) that defines
@@ -39,31 +39,31 @@ Indications that everything is working according to plan include the
'Geiser' minor mode indicator in your mode-line and the appearance of a
new entry for Geiser in the menu bar. If, moreover, the mode-line
indicator is the name of a Scheme implementation, you're indeed in a
-perfect world; otherwise, don't despair and keep on reading: i'll tell
+perfect world; otherwise, don't despair and keep on reading: I'll tell
you how to fix that in a moment.
@cindex geiser-mode commands
-The menu provides a good synopsis of everthing Geiser brings to the
+The menu provides a good synopsis of everything Geiser brings to the
party, including those keyboard shortcuts we Emacsers love. If you're
-seeing the name of your favourite Scheme implementation in the
+seeing the name of your favorites Scheme implementation in the
mode-line, have a running REPL and are comfortable with Emacs, you
can stop reading now and, instead, discover Geiser's joys by yourself.
I've tried to make Geiser as self-documenting as any self-respecting
Emacs package should be. If you follow this route, make sure to take a
look at Geiser's customization buffers (@kbd{M-x customize-group
-...@key{ret} geiser}): there's lot of fine tunning available there. You
+...@key{ret} geiser}): there's lot of fine-tuning available there. You
might also want to take a glance at the @ref{Cheat sheet}.
Since @i{geiser-mode} is a minor mode, you can toggle it with
@kbd{M-x geiser-mode}, and control its activation in hooks with the
functions @code{turn-on-geiser-mode} and @code{turn-off-geiser-mode}.
-If, for some reason i cannot fathom, you prefer @i{geiser-mode} not
+If, for some reason I cannot fathom, you prefer @i{geiser-mode} not
to be active by default, customizing @code{geiser-mode-auto-p} to
@code{nil} will do the trick.
@cindex scheme file extensions
And if you happen to use a funky extension for your Scheme files that is
-not recognised as such by Emacs, just tell her about it with:
+not recognized as such by Emacs, just tell her about it with:
@example
(add-to-list 'auto-mode-alist '("\\.funky-extension\\'" . scheme-mode))
@end example
@@ -78,7 +78,7 @@ how to make sure that that's actually the case.
@node The source and the REPL, Documentation helpers, Activating Geiser, Between the parens
@section The source and the REPL
-As i've already mentioned a couple of times, @i{geiser-mode} needs a
+As I've already mentioned a couple of times, @i{geiser-mode} needs a
running REPL to be operative. Thus, a common usage pattern will be
for you to first call @code{run-geiser} (or one of its variants, see
them described @ref{choosing-impl,,here}), and then open Scheme files;
@@ -125,7 +125,7 @@ If we haven't been lucky this far and you have customized
@code{geiser-default-implementation} to the name of a supported
implementation, we'll follow your lead.
@item
-See? That's the problem of being a smart alec: one's always outsmarted
+See? That's the problem with being a smart aleck: One's always outsmarted
by people around. At this point, @i{geiser-mode} will humbly give up and
ask you to explicitly choose the Scheme implementation.
@end enumerate
@@ -191,7 +191,7 @@ As explained before (@pxref{Modus operandi}), all Geiser activities take
place in the context of the @i{current namespace}, which, for Scheme
buffers, corresponds to the module that the Scheme implementation
associates to the source file at hand (for instance, in Racket, there's
-a one to one correspondence between paths and modules, while Guile
+a one-to-one correspondence between paths and modules, while Guile
relies on explicit @code{define-module} forms in the source file).
Now that we have @code{geiser-mode} happily alive in our Scheme buffers
@@ -207,7 +207,7 @@ can do for us, besides jumping to and fro.
The first thing you will notice by moving around Scheme source is that,
every now and then, the echo area lightens up with the same autodoc
messages we know and love from our REPL forays. This happens every
-time the Scheme process is able to recognise an identifier in the
+time the Scheme process is able to recognize an identifier in the
buffer, and provide information either on its value (for variables) or
on its arity and the name of its formal arguments (for procedures and
macros). That information will only be available if the module the
@@ -237,11 +237,11 @@ enclosed in parenthesis. When an optional argument has a default value
(or a form defining its default value), autodoc will display it after
the argument name. When the optional arguments are keywords, their names
are prefixed with ``#:'' (i.e., their names @i{are} keywords). An
-ellipsis (@dots{}) serves as a marker of an indeterminated number of
+ellipsis (@dots{}) serves as a marker of an indeterminate number of
parameters, as is the case with @i{rest} arguments or when autodoc
cannot fathom the exact number of arguments (this is often the case with
macros defined using @code{syntax-case}). Another way in which autodoc
-displays its ignorance is by using and underscore to display parameters
+displays its ignorance is by using an underscore to display parameters
whose name is beyond its powers.
@img{autodoc-multi, right} It can also be the case that a function or
@@ -259,7 +259,7 @@ parenthesis. After all, we're talking about Scheme here.
is on a symbol corresponding to a plain variable: you'll see in the echo
area its name, preceded by the module where it's defined, and followed
by its value, with an intervening arrow for greater effect. This time,
-there are no enclosing parenthesis (i hope you see the logic in my
+there are no enclosing parenthesis (I hope you see the logic in my
madness).
@cindex autodoc customized
@@ -286,7 +286,7 @@ identifier or module.
@cindex documentation for symbol
@cindex docstrings, maybe
For symbols, the incantation is @kbd{M-x geiser-doc-symbol-at-point}, or
-...@kbd{c-c C-d C-d} for short. If the associated scheme supports
+...@kbd{c-c C-d C-d} for short. If the associated Scheme supports
docstrings (as, for instance, Guile does), you'll be teleported to a new
Emacs buffer displaying Geiser's documentation browser, filled with
information about the identifier, including its docstring (if any;
@@ -316,10 +316,10 @@ exactly as you would do @ref{repl-mod,,in the REPL}.
In both cases, the documentation browser will show a couple of buttons
giving you access to further documentation. First, you'll see a button
named @i{source}: pressing it you'll jump to the symbol's definition.
-The second button, dubbed @i{manual}, will open the scheme
+The second button, dubbed @i{manual}, will open the Scheme
implementation's manual page for the symbol at hand. For Racket, that
will open your web browser displaying the corresponding reference's page
-(using Emacs' @code{browser-url} command), while in Guile a lookup will
+(using Emacs' @code{browser-url} command), while in Guile a look-up will
be performed in the texinfo manual.
@cindex opening manual pages
@@ -336,11 +336,11 @@ navigation commands available in the documentation browser.
@cindex philosophy
@cindex incremental development
One of Geiser's main goals is to facilitate incremental development. You
-might have noticed that i've made a big fuss of Geiser's ability to
+might have noticed that I've made a big fuss of Geiser's ability to
recognize context, by being aware of the namespace where its operations
happen.
-That awareness is specially important when evaluating code in your
+That awareness is especially important when evaluating code in your
scheme buffers, using the commands described below. They allow you to
send code to the running Scheme with a granularity ranging from whole
files to single s-expressions. That code will be evaluated in the module
@@ -383,7 +383,7 @@ For all the commands above, the result of the evaluation is displayed in
the minibuffer, unless it causes a (scheme-side) error (@pxref{To err
perchance to debug}).
-At the risk of repeating myself, i'll remember you that all these
+At the risk of repeating myself, I'll remind you that all these
evaluations will take place in the namespace of the module corresponding
to the Scheme file from which you're sending your code, which, in
general, will be different from the REPL's current module. And, if
@@ -391,7 +391,7 @@ all goes according to plan, (re)defined variables and procedures should
be immediately visible inside and, if exported, outside their module.
Besides evaluating expressions, definitions and regions, you can also
-macro-expand them. The corresponding keybindings start with the prefix
+macro-expand them. The corresponding key bindings start with the prefix
@kbd{C-c C-m} and end, respectively, with @kbd{C-e}, @kbd{C-x} and
@kbd{C-r}. The result of the macro expansion always appears in a pop up
buffer.
@@ -406,7 +406,7 @@ the capabilities of the underlying Scheme REPL.
@cindex error buffer
In Racket, you'll be presented with a backtrace, in a new buffer where
-file paths locating the origin of the error are clickable (you can
+file paths locating the origin of the error are click-able (you can
navigate them using the @key{TAB} key, and use @key{RET} or the mouse to
jump to the offending spot; or invoke Emacs' stock commands
@code{next-error} and @code{previous-error}, bound to @kbd{M-g n} and
@@ -415,7 +415,7 @@ jump to the offending spot; or invoke Emacs' stock commands
@imgc{eval-error}
The Racket backtrace also highlights the exception type, making it
-clickable. Following the link will open the documentation corresponding
+click-able. Following the link will open the documentation corresponding
to said exception type. Both the error and exception link faces are
customizable (@code{geiser-font-lock-error-link} and
@code{geiser-font-lock-doc-link}).
@@ -423,7 +423,7 @@ customizable (@code{geiser-font-lock-error-link} and
On the other hand, Guile's reaction to evaluation errors is different:
it enters the debugger in its REPL. Accordingly, the REPL buffer will
pop up if your evaluation fails in a Guile file, and the error message
-and backtrace will be displayed in there, again clickable and all. But
+and backtrace will be displayed in there, again click-able and all. But
there you have the debugger at your disposal, with the REPL's current
module set to that of the offender, and a host of special debugging
commands that are described in Guile's fine documentation.
@@ -437,8 +437,8 @@ Racket. You can control how picky Guile is reporting warnings by
customizing the variable @code{geiser-guile-warning-level}, whose
detailed docstring (which see, using, e.g. @kbd{C-h v}) allows me to
offer no further explanation here. The customization group
-...@i{geiser-guile} is also worth a glance, for a couple of options to fine
-tune how Geiser interacts with Guile's debugger (and more). Same thing
+...@i{geiser-guile} is also worth a glance, for a couple of options to
+fine-tune how Geiser interacts with Guile's debugger (and more). Same thing
for racketeers and @i{geiser-racket}.
@node Jumping around, Geiser writes for you, To err perchance to debug, Between the parens
@@ -491,7 +491,7 @@ uses the standard Emacs completion machinery to display them. That
means, among other things, that partial completion is available: just
try to complete @code{d-s} or @code{w-o-t-s} to see why this is a good
thing. Partial completion won't work if you have disabled it globally in
-your Emacs configuration: if you don't know what i'm talking about,
+your Emacs configuration: if you don't know what I'm talking about,
never mind: Geiser's partial completion will work for you out of the
box.
diff --git a/doc/repl.texi b/doc/repl.texi
index cfce6c8..e80aa08 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -2,7 +2,7 @@
@chapter The REPL
@anchor{quick-start}
If you've followed the indications in @ref{Setting it up}, your Emacs is
-now ready to start playing. Otherwise, i'll wait for you: when you're
+now ready to start playing. Otherwise, I'll wait for you: when you're
ready, just come back here and proceed to the following sections.
@menu
@@ -18,7 +18,7 @@ ready, just come back here and proceed to the following sections.
@section Starting the REPL
@cindex REPL
-To start a Scheme REPL (meaning, a scheme process offering you a
+To start a Scheme REPL (meaning, a Scheme process offering you a
Read-Eval-Print Loop), Geiser provides the generic interactive command
@command{run-geiser}. If you run it (via, as is customary in Emacs,
@kbd{M-x run-geiser}, you'll be saluted by a prompt asking which one of
@@ -60,7 +60,7 @@ want to use the default.
@cindex Racket's REPL server
In Racket, you have to use the REPL server that comes with Geiser. To
-that end, put Geiser's Racket scheme directory in the Racket's
+that end, put Geiser's Racket Scheme directory in the Racket's
collection search path and invoke @code{start-geiser} (a procedure in
the module @code{geiser/server}) somewhere in your program, passing it
the desired port. This procedure will start the REPL server in a
@@ -80,9 +80,9 @@ Scheme process in a dedicated thread, meaning that your external program
can go on doing whatever it was doing while you tinker with it from
Emacs. Note, however, that all Scheme threads share the heap, so that
you'll be able to interact with those other threads in the running
-scheme from Emacs in a variety of ways. For starters, all your
-(re)defintions will be visible everywhere. That's dangerous, but will
-come in handy when you need to debug your running webserver.
+Scheme from Emacs in a variety of ways. For starters, all your
+(re)definitions will be visible everywhere. That's dangerous, but will
+come in handy when you need to debug your running web-server.
@cindex remote connections
The connection between Emacs and the Scheme process goes over TCP, so it
@@ -95,9 +95,9 @@ tunnel.
@img{repl-menu, right}
@cindex REPL commands
A quick way of seeing what else Geiser's REPL can do for you, is to
-display the corresponding entry up there in your menu bar. No, i don't
+display the corresponding entry up there in your menu bar. No, I don't
normally use menus either; but they can come in handy until you've
-memorized Geiser's commands, as a learning device. And yes, i usually
+memorized Geiser's commands, as a learning device. And yes, I usually
run Emacs inside a terminal, but one can always use
@uref{http://www.emacswiki.org/emacs/LaCarte, La Carte} to access the
menus in a convenient enough fashion.
@@ -111,7 +111,7 @@ is, they'll find the previous or next sexp that starts with the current
input prefix (defined as the text between the end of the prompt and your
current position, a.k.a. @dfn{point}, in the buffer). For going up and
down the list unconditionally, just use @kbd{C-c M-p} and @kbd{C-c M-n}.
-In addition, navigation is sexp- rather than line-based.
+In addition, navigation is sexp-based rather than line-based.
There are also a few commands to twiddle with the Scheme process.
@kbd{C-c C-q} will gently ask it to quit, while @kbd{C-u C-c C-q} will
@@ -142,7 +142,7 @@ will be happy to oblige.
@cindex current module, change
Once you enter a new module, only those bindings visible in its
-namespace will be available to your evaluations. All schemes supported
+namespace will be available to your evaluations. All Schemes supported
by Geiser provide a way to import new modules in the current namespace.
Again, there's a Geiser command, @command{geiser-repl-import-module}, to
invoke such functionality, bound this time to @kbd{C-c C-i}. And, again,
@@ -198,7 +198,7 @@ those questions too.
Actually, if you've been playing with the REPL as you read, you might
have notice some frantic activity taking place in the minibuffer every
now and then. That was Geiser trying to be helpful (while, hopefully,
-not being clippy), or, more concretely, what i call, for want of a
+not being clippy), or, more concretely, what I call, for want of a
better name, its @dfn{autodoc} mode. Whenever it's active (did you
notice that @i{A} in the mode-line?), Geiser's gerbils will be scanning
what you type and showing (unless you silent them with @kbd{C-c C-a})
@@ -243,7 +243,7 @@ If that's still not enough, Geiser can jump, via @kbd{M-.}, to the
symbol's definition. A buffer with the corresponding file will pop up,
with its point resting upon the identifier's defining form. When you're
done inspecting, @kbd{M-,} will bring you back to where you were. As we
-will see, these commands are also available in scheme buffers. @kbd{M-.}
+will see, these commands are also available in Scheme buffers. @kbd{M-.}
also works for modules: if your point is on an unambiguous module name,
the file where it's defined will be opened for you.
@@ -255,7 +255,7 @@ The looks and ways of the REPL can be fine-tuned via a bunch of
customization variables. You can see and modify them all in the
corresponding customization group (by using the menu entry or the good
old @kbd{M-x customize-group geiser-repl}), or by setting them in your
-Emacs initialization files (as a rule, all knobs in Geiser are turnable
+Emacs initialization files (as a rule, all knobs in Geiser are tunable
this way: you don't need to use customization buffers if you don't like
them).
@@ -275,7 +275,7 @@ forget about the richness of the Scheme ecosystem with something like
@example
(setq geiser-active-implementations '(racket))
@end example
-...@noindent in your initialisation files.
+...@noindent in your initialization files.
@cindex scheme binary
@cindex scheme executable path
@@ -289,10 +289,10 @@ full path to the requisite binary.
@cindex scheme init file
@cindex GUILE_LOAD_PATH
@cindex PLTCOLLECTS
-You can also specify a couple more initialisation parameters. For Guile,
+You can also specify a couple more initialization parameters. For Guile,
@code{geiser-guile-load-path} is a list of paths to add to its load path
when it's started, while @code{geiser-guile-init-file} is the path to an
-initialisation file to be loaded on startup. The equivalent variables
+initialization file to be loaded on start-up. The equivalent variables
for Racket are @code{geiser-racket-collects} and
@code{geiser-racket-init-file}.
@@ -319,16 +319,16 @@ If you happen to love peace and quiet and prefer to keep your REPL's
echo area free from autodoc's noise, @code{geiser-repl-autodoc-p} is the
customization variable for you: set it to @code{nil} and autodoc will be
disabled by default in new REPLs. You can always bring the fairies
-back, on a per REPL basis, using @kbd{C-c C-a}.
+back, on a per-REPL basis, using @kbd{C-c C-a}.
@subsubheading Remote connections
@cindex port, default
@cindex host, default
When using @code{connect-to-guile} or @code{geiser-connect}, you'll be
-prompted for a host and a port, defaulting to localhost and 37146. You
+prompted for a host and a port, defaulting to ``localhost'' and 37146. You
can change those defaults customizing @code{geiser-repl-default-host}
-and @code{geiser-repl-default-port}, respectfully.
+and @code{geiser-repl-default-port}, respectively.
@c Local Variables:
@c mode: texinfo
diff --git a/doc/thanks.texi b/doc/thanks.texi
index 4d9662d..e551ffc 100644
--- a/doc/thanks.texi
+++ b/doc/thanks.texi
@@ -22,7 +22,7 @@ questions.
Matthew Flatt, Robby Findler and the rest of the PLT team did not only
answer my inquiries, but provided almost instant fixes to the few
-issues i found.
+issues I found.
Thanks also to the PLT and Guile communities, for showing me that
Geiser was not only possible, but a pleasure to hack on. And to the
diff --git a/doc/top.texi b/doc/top.texi
index 2f218c4..4a1683c 100644
--- a/doc/top.texi
+++ b/doc/top.texi
@@ -7,15 +7,15 @@ to make Scheme hacking inside Emacs (even more) fun.
@cindex derailment
@cindex corpses
@cindex philosophy
-Or, to be precise, what @uref{http://hacks-galore.org/jao, i} consider
+Or, to be precise, what @uref{http://hacks-galore.org/jao, I} consider
fun. Geiser is thus my humble contribution to the dynamic school of
-expression, and a reaction against what i perceive as a derailment, in
-modern times, of standard Scheme towards the static camp. Because i
+expression, and a reaction against what I perceive as a derailment, in
+modern times, of standard Scheme towards the static camp. Because I
prefer growing and healing to poking at corpses, the continuously
running Scheme interpreter takes the center of the stage in Geiser. A
bundle of Elisp shims orchestrates the dialog between the Scheme
interpreter, Emacs and, ultimately, the schemer, giving her access to
-live metadata. Here's how.
+live meta-data. Here's how.
@c Local Variables:
@c mode: texinfo
