summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/fun.texi5
-rw-r--r--doc/repl.texi4
2 files changed, 7 insertions, 2 deletions
diff --git a/doc/fun.texi b/doc/fun.texi
index 9895443..eba54e1 100644
--- a/doc/fun.texi
+++ b/doc/fun.texi
@@ -430,7 +430,10 @@ This one feature is as sweet as easy to explain: @kbd{M-.}
(@code{geiser-edit-symbol-at-point}) will open the file where the
identifier around point is defined and land your point on its
definition. To return to where you were, press @kbd{M-,}
-(@code{geiser-pop-symbol-stack}).
+(@code{geiser-pop-symbol-stack}). This command works also for module
+names: Geiser first tries to locate a definition for the identifier at
+point and, if that fails, a module with that name; if the latter
+succeeds, the file where the module is defined will pop up.
Sometimes, the underlying Scheme will tell Geiser only the file where
the symbol is defined, but Geiser will use some heuristics (read,
diff --git a/doc/repl.texi b/doc/repl.texi
index 6a4c47d..43a07b4 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -208,7 +208,9 @@ If that's still not enough, Geiser can jump, via @kbd{M-.}, to the
symbol's definition. A buffer with the corresponding file will pop up,
with its point resting upon the identifier's defining form. When you're
done inspecting, @kbd{M-,} will bring you back to where you were. As we
-will see, these commands are also available in scheme buffers.
+will see, these commands are also available in scheme buffers. @kbd{M-.}
+also works for modules: if your point is on an unambiguous module name,
+the file where it's defined will be opened for you.
@cindex module exports
@anchor{repl-mod}