diff options
Diffstat (limited to 'doc/fun.texi')
| -rw-r--r-- | doc/fun.texi | 20 |
1 files changed, 14 insertions, 6 deletions
diff --git a/doc/fun.texi b/doc/fun.texi index e56af68..b2a0e5f 100644 --- a/doc/fun.texi +++ b/doc/fun.texi @@ -340,7 +340,10 @@ region. Again, there's an @i{and go} version available, For all the commands above, the result of the evaluation is displayed in the minibuffer, unless it causes a (scheme-side) error, in which case Geiser will report the problem by opening a debug buffer with -information on what went wrong. +information on what went wrong (Racket) or jump into the debugger when +the REPL provides such a beast (Guile). + +@image{img/eval-error} At the risk of repeating myself, i'll remember you that all these evaluations will take place in the namespace of the module corresponding @@ -357,18 +360,23 @@ buffer. When an error occurs during evaluation, you'll be presented with a backtrace, in a new buffer where file paths locating the origin of the -error are clickable (you can navigate them using the @key{TAB} key). +error are clickable (you can navigate them using the @key{TAB} key, and +use @key{RET} or the mouse to jump to the offending spot). @node Jumping around, Geiser writes for you, Evaluating Scheme code, Fun between the parens @section Jumping around -This one feature is as sweet as easy to explain: @kbd{M-.} 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-,}. +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}).. Sometimes, the underlying Scheme will tell Geiser only the file where the symbol is defined, but Geiser will use some heuristics (read, -regular expressions) to locate the exact line and bring you there. +regular expressions) to locate the exact line and bring you there. Thus, +if you find Geiser systematically missing your definitions, send a +message to the mailing list and we'll try to make the algorithm smarter. You can control how the destination buffer pops up by setting @code{geiser-edit-symbol-method} to either @code{nil} (to open the file |