summaryrefslogtreecommitdiff
path: root/doc/repl.texi
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2012-09-08 19:24:10 +0200
committerJose Antonio Ortega Ruiz <jao@gnu.org>2012-09-08 19:24:10 +0200
commit977335378247e8c7df0594fc300cb82c4ce6bbc7 (patch)
tree35c9292bdf372cc596f3e7de9331a667a526a212 /doc/repl.texi
parent97f2fb5b47aaeec00cdcd1c6082e95c907eb3f62 (diff)
downloadgeiser-guile-977335378247e8c7df0594fc300cb82c4ce6bbc7.tar.gz
geiser-guile-977335378247e8c7df0594fc300cb82c4ce6bbc7.tar.bz2
Racket: new option to specify network interface for REPL server
In geiser-racket.sh, there's the new option -n, which uses a new hostname argument accepted by geiser/user's start-geiser function.
Diffstat (limited to 'doc/repl.texi')
-rw-r--r--doc/repl.texi11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/repl.texi b/doc/repl.texi
index 560f3eb..dcc1bd0 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -75,11 +75,12 @@ In Racket, you have to use the REPL server that comes with Geiser. To
that end, put Geiser's Racket @file{scheme} directory in 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
-separate thread. For an example of how to do that, see the script
-@file{bin/geiser-racket.sh} in the source distribution, or, if you've
-compiled Geiser, @file{bin/geiser-racket-noinst} in the build directory,
-or, if you've installed Geiser, @file{geiser-racket} in
+the desired port and, if desired, network interface name. This
+procedure will start the REPL server in a separate thread. For an
+example of how to do that, see the script @file{bin/geiser-racket.sh} in
+the source distribution, or, if you've compiled Geiser,
+@file{bin/geiser-racket-noinst} in the build directory, or, if you've
+installed Geiser, @file{geiser-racket} in
@file{<installation-prefix>/bin}. These scripts start a new interactive
Racket that is also running a REPL server (they also load the errortrace
library to provide better diagnostics, but that's not strictly needed).