summaryrefslogtreecommitdiff
path: root/doc/repl.texi
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2010-08-21 00:37:39 +0200
committerJose Antonio Ortega Ruiz <jao@gnu.org>2010-08-21 00:37:39 +0200
commit2319ffac96cca89f1df49d49e05da10652ac1afb (patch)
tree31385f1d5ae68463a7759c92b636c5f2b99850be /doc/repl.texi
parent103cfbb94a50c608d1c8510970bbfd9278bcd2f3 (diff)
downloadgeiser-2319ffac96cca89f1df49d49e05da10652ac1afb.tar.gz
geiser-2319ffac96cca89f1df49d49e05da10652ac1afb.tar.bz2
In texinfo, @var is for meta-variables, not regular ones
Diffstat (limited to 'doc/repl.texi')
-rw-r--r--doc/repl.texi12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/repl.texi b/doc/repl.texi
index 8a73771..124d509 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -199,7 +199,7 @@ some related tips.
Instead of using the generic @command{run-geiser} command, you can start
directly your Scheme of choice via @command{run-racket} or
@command{run-guile}. @anchor{active-implementations} In addition, the
-variable @var{geiser-active-implementations} contains a list of those
+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
@@ -210,17 +210,17 @@ forget about the richness of the Scheme ecosystem with something like
@anchor{impl-binary} When starting a new REPL, Geiser assumes, by
default, that the corresponding Scheme binary is in your path. If that's
-not the case, the variables to tweak are @var{geiser-guile-binary} and
-@var{geiser-racket-binary}, which should be set to a string with the
+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.
@subsubheading History
By default, Geiser won't record duplicates in your input history. If you
-prefer it did, just set @var{geiser-repl-history-no-dups-p} to
+prefer it did, just set @code{geiser-repl-history-no-dups-p} to
@code{nil}. History entries are persistent across REPL sessions: they're
saved in implementation-specific files whose location is controlled by
-the variable @var{geiser-repl-history-filename}. For example, my Geiser
+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")
@@ -232,7 +232,7 @@ directory.
@subsubheading Autodoc
If you happen to love peace and quiet and prefer to keep your REPL's
-echo area free from autodoc's noise, @var{geiser-repl-autodoc-p} is the
+echo area free from autodoc's noise, @code{geiser-repl-autodoc-p} is the
customization variable for you: set it to @code{nil} and autodoc will be
disabled by default in new REPLs. You can always bring the fairies back,
on a per REPL basis, using @kbd{C-c C-a}.