From 724decb06c4757506da489794651b70f778f97b8 Mon Sep 17 00:00:00 2001 From: Jose Antonio Ortega Ruiz Date: Sat, 8 Jan 2011 22:20:23 +0100 Subject: Info formatting (whitespace around code blocks) --- doc/repl.texi | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'doc/repl.texi') 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. -- cgit v1.2.3