diff options
author | Jose Antonio Ortega Ruiz <jao@gnu.org> | 2011-01-08 22:20:23 +0100 |
---|---|---|
committer | Jose Antonio Ortega Ruiz <jao@gnu.org> | 2011-01-08 22:20:23 +0100 |
commit | 963b9d4214a04f2d1c13230d5e69f3e422819d99 (patch) | |
tree | c83784349a51ed1d23b452747ad74590db28355e /doc/repl.texi | |
parent | e2710ee3d9ccffebe67f9a1b16fb7cf88a789655 (diff) | |
download | geiser-chez-963b9d4214a04f2d1c13230d5e69f3e422819d99.tar.gz geiser-chez-963b9d4214a04f2d1c13230d5e69f3e422819d99.tar.bz2 |
Info formatting (whitespace around code blocks)
Diffstat (limited to 'doc/repl.texi')
-rw-r--r-- | doc/repl.texi | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/repl.texi b/doc/repl.texi index 3b722c2..0f0a2cd 100644 --- a/doc/repl.texi +++ b/doc/repl.texi @@ -272,9 +272,11 @@ variable @code{geiser-active-implementations} contains a list of those Schemes Geiser should be aware of. Thus, if you happen to be, say, a racketeer not to be beguiled by other schemes, you can tell Geiser to forget about the richness of the Scheme ecosystem with something like + @example (setq geiser-active-implementations '(racket)) @end example + @noindent in your initialisation files. @cindex scheme binary @@ -304,9 +306,11 @@ prefer it did, just set @code{geiser-repl-history-no-dups-p} to they're saved in implementation-specific files whose location is controlled by the variable @code{geiser-repl-history-filename}. For example, my Geiser configuration includes the following line: + @example (setq geiser-repl-history-filename "~/.emacs.d/geiser-history") @end example + @noindent which makes the files @file{geiser-history.guile} and @file{geiser-history.racket} to live inside my home's @file{.emacs.d} directory. |