summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2010-10-11 03:10:30 +0200
committerJose Antonio Ortega Ruiz <jao@gnu.org>2010-10-11 03:10:30 +0200
commita680bcf2c24eb97b61bc4a3b5b043740b9064887 (patch)
treeba14843b2355c13b13e1ff646012349a30e7d5b4
parentaa3b4233fd2ce19bd3de6759173172e014ef2f63 (diff)
downloadgeiser-chez-a680bcf2c24eb97b61bc4a3b5b043740b9064887.tar.gz
geiser-chez-a680bcf2c24eb97b61bc4a3b5b043740b9064887.tar.bz2
Documentation for remote REPLs
-rw-r--r--doc/repl.texi14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/repl.texi b/doc/repl.texi
index ca61198..f8f3dc9 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -45,6 +45,20 @@ evaluation when they're complete, and will indent new lines properly
until then. It will also keep track of your input, maintaining a history
file that will be reloaded whenever you restart the @repl{}.
+@cindex remote REPL
+@cindex connect to server
+If you use Guile, there's an alternative way of starting a Geiser REPL:
+you can connect to a remote Guile process, provided the latter is
+running a REPL server. For that to happen, you just need to start your
+Guile process (outside Emacs) passing to it the flag @code{--listen}.
+Then, come back to Emacs and execute @kbd{M-x connect-to-guile}. You'll
+be asked for a host and a port, with suitable default values (Guile's
+@code{--listen} flag accepts an optional port as argument (as in
+@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.
+
Nothing that fanciful this far, but there's more to Geiser's @repl{}. On
to the next section!