summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2010-11-06 12:37:07 +0100
committerJose Antonio Ortega Ruiz <jao@gnu.org>2010-11-06 12:37:07 +0100
commit545ed6843fb39f6ed6ef6d7cb28fe8e4cc07e1c5 (patch)
tree9216d5a57b9022fb41158e4b5856859b57ee9baf /doc
parent0320e46e6babf242450dc7e2ade6803213a52090 (diff)
downloadgeiser-guile-545ed6843fb39f6ed6ef6d7cb28fe8e4cc07e1c5.tar.gz
geiser-guile-545ed6843fb39f6ed6ef6d7cb28fe8e4cc07e1c5.tar.bz2
Manual: more precise docs on completion
Diffstat (limited to 'doc')
-rw-r--r--doc/fun.texi8
-rw-r--r--doc/repl.texi13
2 files changed, 13 insertions, 8 deletions
diff --git a/doc/fun.texi b/doc/fun.texi
index f7a5238..08bdc33 100644
--- a/doc/fun.texi
+++ b/doc/fun.texi
@@ -476,9 +476,11 @@ smarty pants mode always on in Scheme buffers, customize
@code{geiser-mode-smart-tab-p} to @code{t}.
@cindex completion for module names
-Geiser also knows how to complete module names, but it's not yet smart
-enough to infer by context that that's what you want. Instead, you must
-use a separate command, bound to @kbd{M-`} (that's a backtick).
+Geiser also knows how to complete module names: if no completion for the
+prefix at point is found among the currently visible bindings, it will
+try to find a module name that matches it. You can also request
+explicitly completion only over module names using @kbd{M-`} (that's a
+backtick).
@c Local Variables:
@c mode: texinfo
diff --git a/doc/repl.texi b/doc/repl.texi
index 19658fb..d1ffc08 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -153,7 +153,8 @@ the @repl{} buffer itself. There, you can use either @kbd{C-.} or
identifiers are bound in the current module and show you a list of those
starting with the prefix at point. Needless to say, this is not a static
list, and it will grow as you define or import new bindings in the
-namespace at hand.
+namespace at hand. If no completion is found, @kbd{@key{TAB}} will try
+to complete the prefix after point as a module name.
REPL buffers use Emacs' compilation mode to highlight errors reported by
the Scheme interpreter, and you can use the @command{next-error} command
@@ -164,7 +165,9 @@ evaluation request, if any. If you prefer a not so forgetful REPL, set
the customization variable @code{geiser-repl-forget-old-errors-p} to
@code{nil}. Note, however, that even when that variable is left as
@kbd{t}, you can always jump to an old error by moving to its line at
-the REPL and pressing return.
+the REPL and pressing @kbd{RET}. When your cursor is away from the last
+prompt, @kbd{TAB} will move to the next error in the buffer, and you can
+use @kbd{BACKTAB} everywhere to go to the previous one.
@node Autodoc and friends, Customization and tips, Completion and error handling, The REPL
@section Autodoc and friends
@@ -223,9 +226,9 @@ identifiers exported by a given module: all you need to do is press
The list of exported bindings is shown in a buffer belonging to Geiser's
documentation browser, of which more details are given in forthcoming
sections (but just perusing its associated key bindings, by any of the
-methods we've already used for the @repl{}, will give you enough
-information to use it effectively enough). Racketeers will be pleased (i
-hope) to note that contracts are part of the information displayed.
+methods we've already mentioned, will give you enough information to use
+it). Racketeers will be pleased (i hope) to note that contracts are part
+of the information displayed.
@node Customization and tips, , Autodoc and friends, The REPL
@section Customization and tips