summaryrefslogtreecommitdiff
path: root/doc/repl.texi
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2013-09-25 05:10:00 +0200
committerJose Antonio Ortega Ruiz <jao@gnu.org>2013-09-25 05:10:00 +0200
commit2cb40f5a1f0115a995daa176208f76b674dd523e (patch)
tree815faf64ef3c8a212145a159dd35aaba7023d376 /doc/repl.texi
parent438e26d9e1759b85785637efc0b64e818e289e57 (diff)
downloadgeiser-chez-2cb40f5a1f0115a995daa176208f76b674dd523e.tar.gz
geiser-chez-2cb40f5a1f0115a995daa176208f76b674dd523e.tar.bz2
Scheme version checks
And, if you happen to be launching it all the time, a way of skipping them via a customizable variable. Should address issue #15.
Diffstat (limited to 'doc/repl.texi')
-rw-r--r--doc/repl.texi23
1 files changed, 17 insertions, 6 deletions
diff --git a/doc/repl.texi b/doc/repl.texi
index 8b32de7..acab26e 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -345,16 +345,27 @@ not the case, the variables to tweak are @code{geiser-guile-binary} and
@code{geiser-racket-binary}, which should be set to a string with the
full path to the requisite binary.
+@cindex Version checking
+Before starting the REPL, Geiser will check wether the version of your
+Scheme interpreter is good enough. This means that it will spend a
+couple tenths of a second launching and quickly discarding a Scheme
+process, but also that the error message you'll get if you're on the
+wrong Scheme version will be much more informative. If you one to
+avoid version checks, just check
+@code{geiser-repl-skip-version-check-p} to @code{t} in your
+configuration.
+
@cindex scheme load path
@cindex scheme init file
@cindex GUILE_LOAD_PATH
+@cindex GUILE_LOAD_COMPILED_PATH
@cindex PLTCOLLECTS
-You can also specify a couple more initialisation parameters. For Guile,
-@code{geiser-guile-load-path} is a list of paths to add to its load path
-when it's started, while @code{geiser-guile-init-file} is the path to an
-initialisation file to be loaded on start-up. The equivalent variables
-for Racket are @code{geiser-racket-collects} and
-@code{geiser-racket-init-file}.
+You can also specify a couple more initialisation parameters. For
+Guile, @code{geiser-guile-load-path} is a list of paths to add to its
+load path (and its compiled load path) when it's started, while
+@code{geiser-guile-init-file} is the path to an initialisation file to
+be loaded on start-up. The equivalent variables for Racket are
+@code{geiser-racket-collects} and @code{geiser-racket-init-file}.
Note, however, that specifying @code{geiser-guile-init-file} is @i{not}
equivalent to changing Guile's initialization file (@file{~/.guile}),