summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2010-10-15 16:56:23 +0200
committerJose Antonio Ortega Ruiz <jao@gnu.org>2010-10-15 16:56:23 +0200
commitdd9afea0677c99620a1543e06e86712465728681 (patch)
treeed620f71f92a61828f1bbc7b6fd175b33de9dbdd
parent28e90a3c097fc903765cdcbfd2a0bdac4a37c444 (diff)
downloadgeiser-chez-dd9afea0677c99620a1543e06e86712465728681.tar.gz
geiser-chez-dd9afea0677c99620a1543e06e86712465728681.tar.bz2
Documentation bit
-rw-r--r--doc/repl.texi7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/repl.texi b/doc/repl.texi
index 173c2cb..6a4c47d 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -57,7 +57,12 @@ be asked for a host and a port, with suitable default values (Guile's
@code{--listen=1969}), if you don't want to use the default). And voila,
you'll have a Geiser REPL that is served by the remote Guile process in
a dedicated thread, meaning that your Guile can go on doing whatever it
-was doing while you tinker with it from Emacs.
+was doing while you tinker with it from Emacs. Note, however,
+that all Guile 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 you (re)defintions will be visible
+everywhere. That's dangerous, but will come in handy when you need to
+debug your running webserver.
Nothing that fanciful this far, but there's more to Geiser's @repl{}. On
to the next section!