summaryrefslogtreecommitdiff
path: root/doc/repl.texi
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2010-11-11 03:01:33 +0100
committerJose Antonio Ortega Ruiz <jao@gnu.org>2010-11-11 03:01:33 +0100
commitdfc900c0e2f59edfb06bbdabfc4bcde172d6ced9 (patch)
treeff2937e287b418520e082d06907e5027601e4eee /doc/repl.texi
parent3db4017f11317c497fba0e97adb5fd1a18ca4534 (diff)
downloadgeiser-guile-dfc900c0e2f59edfb06bbdabfc4bcde172d6ced9.tar.gz
geiser-guile-dfc900c0e2f59edfb06bbdabfc4bcde172d6ced9.tar.bz2
Partial work (connections working)
Diffstat (limited to 'doc/repl.texi')
-rw-r--r--doc/repl.texi13
1 files changed, 4 insertions, 9 deletions
diff --git a/doc/repl.texi b/doc/repl.texi
index 03fb42a..aefa432 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -118,15 +118,10 @@ There are also a few commands to twiddle with the Scheme process.
mercilessly kill the process (but not before stowing your history in the
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}).
+process alone. 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.