summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2010-10-11 03:26:56 +0200
committerJose Antonio Ortega Ruiz <jao@gnu.org>2010-10-11 03:26:56 +0200
commit11bde7b13d2152d3d5ee6d70bee1b8743528b89d (patch)
tree3001cc6c0ff7f1a89962e284354ddab28747716a /doc
parent302264eea160758738a9bc160af2c8cbe0428363 (diff)
downloadgeiser-11bde7b13d2152d3d5ee6d70bee1b8743528b89d.tar.gz
geiser-11bde7b13d2152d3d5ee6d70bee1b8743528b89d.tar.bz2
A bit more documentation on remote REPLs
Diffstat (limited to 'doc')
-rw-r--r--doc/repl.texi27
1 files changed, 18 insertions, 9 deletions
diff --git a/doc/repl.texi b/doc/repl.texi
index f8f3dc9..64bee96 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -89,15 +89,17 @@ In addition, navigation is sexp- 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
mercilessly kill the process (but not before stowing your history in the
-file system). A softer nuke is performed by @kbd{C-c C-k}: some (rare, i
-promise) times, Geiser's @repl{} can get confused by the input received
-from then underlying Scheme (specially if you have multiple threads
-writing to the standard ports), and become irresponsive; you can try
-this command to try to revive it without killing the process. Finally,
-if worse comes to worst and the process is dead, @kbd{C-c C-z} will
-restart it (but the same shortcut, issued when the @repl{} is alive,
-will bring you back to the buffer you came from, as explained
-@ref{switching-repl-buff,,here}).
+file system). Unless you're using a remote REPL, that is, in which case
+both commands will just sever the connection and leave the remote
+process alone. A softer nuke is performed by @kbd{C-c C-k}: some (rare,
+i promise) times, Geiser's @repl{} can get confused by the input
+received from then underlying Scheme (specially if you have multiple
+threads writing to the standard ports), and become irresponsive; you can
+try this command to try to revive it without killing the process or
+closing your connection. Finally, if worse comes to worst and the
+process is dead, @kbd{C-c C-z} will restart it (but the same shortcut,
+issued when the @repl{} is alive, will bring you back to the buffer you
+came from, as explained @ref{switching-repl-buff,,here}).
The remaining commands are meatier, and deserve sections of their own.
@@ -291,6 +293,13 @@ customization variable for you: set it to @code{nil} and autodoc will be
disabled by default in new @repl{}s. You can always bring the fairies
back, on a per @repl{} basis, using @kbd{C-c C-a}.
+@subsubheading Remote connections
+
+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
+can change those defaults customizing @code{geiser-repl-default-host}
+and @code{geiser-repl-default-port}, respectfully.
+
@c Local Variables:
@c mode: texinfo
@c TeX-master: "geiser"