Here is a set of patches based on the following recommendations from
the Texinfo manual:
1) Node: (texinfo) example
"The lines containing `...@example' and `...@end example' will disappear
from the output. To make the output look good, you should put a blank
line before the `...@example' and another blank line after the `...@end
example'."
"Examples are often, logically speaking, "in the middle" of a
paragraph, and the text that continues afterwards should not be
indented, as in the example above. The `...@noindent' command prevents a
piece of text from being indented as if it were a new paragraph
(*no...@noindent'." [sic]
2) Node: (texinfo) noindent
"It is best to write `...@noindent' on a line by itself, since in most
environments, spaces following the command will not be ignored."
So, a blank line was added before each @example and after each
'@end example' line. Likewise, for @enumerate/@end enumerate.
This makes the TeX and Info text look uncrowded as the HTML text
already does.
Also, all text that followed @noindent macros on the same line were
moved to the next line, and continuing text that followed '@end example'
lines that did not have an @noindent macro got one added.
-
diff --git a/doc/install.texi b/doc/install.texi
index 745f398..38703e0 100644
--- a/doc/install.texi
+++ b/doc/install.texi
@@ -52,6 +52,7 @@ git clone git://git.sv.gnu.org/geiser.git
git clone http://git.sv.gnu.org/r/geiser.git
@end example
+...@noindent
You can also follow Geiser's development in
@uref{https://github.com/jaor/geiser, one}
@uref{http://repo.or.cz/w/geiser.git, or}
@@ -181,6 +182,7 @@ also probably a good idea to require @code{quack} @i{after} loading
@file{geiser.el} (or requiring a compiled version).
@end itemize
+...@noindent
You just need to install and setup them as usual, for every package's
definition of usual. Geiser will notice their presence and react
accordingly.
diff --git a/doc/parens.texi b/doc/parens.texi
index b72e03f..89b60a1 100644
--- a/doc/parens.texi
+++ b/doc/parens.texi
@@ -103,6 +103,7 @@ subsection}.
@cindex scheme implementation, choosing
To determine what Scheme implementation corresponds to a given source
file, Geiser uses the following algorithm:
+
@enumerate
@item
If the file-local variable @code{geiser-scheme-implementation} is
@@ -137,6 +138,7 @@ See? That's the problem of being a smart aleck: one's always outsmarted
by people around. At this point, @i{geiser-mode} will humbly give up and
ask you to explicitly choose the Scheme implementation.
@end enumerate
+
As you can see in the list above, there are several ways to influence
Geiser's guessing by mean customizable variables. The most direct (and
most impoverishing) is probably limiting the active implementations to a
@@ -150,7 +152,8 @@ default value for the latter variable:
((regexp "\\.rkt$") racket))
@end example
-...@noindent which describes the simple heuristic that files with @file{.scm} as
+...@noindent
+which describes the simple heuristic that files with @file{.scm} as
extension are by default associated to a Guile REPL while those ending
in @file{.ss} or @file{.rkt} correspond to Racket's implementation (with
the caveat that these rules are applied only if the previous heuristics
@@ -286,7 +289,7 @@ madness).
You can change the way Geiser displays the module/identifier combo by
customizing @code{geiser-autodoc-identifier-format}. For example, if you
wanted a tilde surrounded by spaces instead of a colon as a separator,
-you would write something like
+you would write something like:
@example
(setq geiser-autodoc-identifier-format "%s ~ %s")
diff --git a/doc/repl.texi b/doc/repl.texi
index 03361fd..bded2b7 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -282,13 +282,14 @@ directly your Scheme of choice via @command{run-racket} or
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
+forget about the richness of the Scheme ecosystem with something like:
@example
(setq geiser-active-implementations '(racket))
@end example
-...@noindent in your initialisation files.
+...@noindent
+in your initialisation files.
@cindex scheme binary
@cindex scheme executable path
@@ -322,7 +323,8 @@ example, my Geiser configuration includes the following line:
(setq geiser-repl-history-filename "~/.emacs.d/geiser-history")
@end example
-...@noindent which makes the files @file{geiser-history.guile} and
+...@noindent
+which makes the files @file{geiser-history.guile} and
@file{geiser-history.racket} to live inside my home's @file{.emacs.d}
directory.
