summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjao <jao@numenor.local>2011-05-01 18:04:30 -0700
committerjao <jao@numenor.local>2011-05-01 18:04:30 -0700
commitbe04e20fb0864b09395c5bd55783033e82145148 (patch)
treef0a6a8d7d06d11ba475a8b35be164ed2e229546d /doc
parentce2153a84d13e1e672a6ca6fd4c9144cac585c10 (diff)
downloadgeiser-be04e20fb0864b09395c5bd55783033e82145148.tar.gz
geiser-be04e20fb0864b09395c5bd55783033e82145148.tar.bz2
Documentation fixes courtesy of M. Harig
In this episode, we learn how to use @ escapes in texinfo urls.
Diffstat (limited to 'doc')
-rw-r--r--doc/macros.texi4
-rw-r--r--doc/parens.texi4
-rw-r--r--doc/repl.texi14
-rw-r--r--doc/thanks.texi12
4 files changed, 17 insertions, 17 deletions
diff --git a/doc/macros.texi b/doc/macros.texi
index 29e6321..8b3e325 100644
--- a/doc/macros.texi
+++ b/doc/macros.texi
@@ -2,11 +2,11 @@
@set GUILE_VERSION 2.0
@set RACKET_VERSION 5.0.1
@set EMACS_VERSION 23.2
-@set DOWN_BASE http://download.savannah.nongnu.org/releases/geiser
+@set DOWN_BASE http://download.savannah.nongnu.org/@/releases/@/geiser
@set TARBALL geiser-@value{VERSION}.tar.gz
@macro downfile{FILE, CAPT}
-@uref{@value{DOWN_BASE}/@value{VERSION}/\FILE\, \CAPT\}
+@uref{@value{DOWN_BASE}/@/@value{VERSION}/@/\FILE\, \CAPT\}
@end macro
@macro vblurb{GVERS, RVERS, DATE}
diff --git a/doc/parens.texi b/doc/parens.texi
index 7c83f8e..a41057a 100644
--- a/doc/parens.texi
+++ b/doc/parens.texi
@@ -408,11 +408,11 @@ uses of a macro after redefining it. That's not a limitation imposed by
Geiser, but a consequence of how macros work in Scheme (and other
Lisps). There's also the risk that you lose track of what's actually
defined and what's not during a given session. But,
-@uref{http://programming-musings.org/2009/03/29/from-my-cold-prying-hands/,in
+@uref{http://programming-musings.org/@/2009/03/29/@/from-my-cold-prying-hands/,in
my opinion}, those are limitations we lispers are aware of, and they
don't force us to throw the baby with the bathwater and ditch
incremental evaluation. Some people disagree; if you happen to find
-@uref{http://blog.racket-lang.org/2009/03/drscheme-repl-isnt-lisp.html,
+@uref{http://blog.racket-lang.org/@/2009/@/03/@/drscheme-repl-isnt-lisp.html,
their arguments} convincing, you don't have to throw away Geiser
together with the baby: @kbd{M-x geiser-restart-repl} will let you
restart the REPL as many times as you see fit.
diff --git a/doc/repl.texi b/doc/repl.texi
index 14a9397..bef0f3f 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -321,13 +321,13 @@ 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 init file (@file{~/.guile}), because the
-former is loaded using the @code{-l} flag, together with @code{-q} to
-disable loading the second. But there are subtle differences in the way
-Guile loads the init file vs. how it loads a file specifed via the
-@code{-l} flag. If what you want is just loading @file{~/.guile}, leave
-@code{geiser-guile-init-file} alone and set
-@code{geiser-guile-load-init-file-p} to @code{t} instead.
+equivalent to changing Guile's initialization file (@file{~/.guile}),
+because the former is loaded using the @code{-l} flag, together with
+@code{-q} to disable loading the second. But there are subtle
+differences in the way Guile loads the initialization file versus how it
+loads a file specified via the @code{-l} flag. If what you want is just
+loading @file{~/.guile}, leave @code{geiser-guile-init-file} alone and
+set @code{geiser-guile-load-init-file-p} to @code{t} instead.
@subsubheading History
diff --git a/doc/thanks.texi b/doc/thanks.texi
index 0de9241..42eb41d 100644
--- a/doc/thanks.texi
+++ b/doc/thanks.texi
@@ -38,22 +38,22 @@ Slime hackers, who led the way.
For questions, praise, critique and anything else Geiser, do not
hesitate to drop an email to our list, @i{(@@ geiser-users (. nongnu
org))}: no subscription required. Check
-@uref{http://lists.nongnu.org/mailman/listinfo/geiser-users, the list
+@uref{http://lists.nongnu.org/@/mailman/@/listinfo/@/geiser-users, the list
page} for more information or browse
-@uref{http://lists.nongnu.org/archive/html/geiser-users/, the archives}.
+@uref{http://lists.nongnu.org/@/archive/@/html/@/geiser-users/, the archives}.
The list is also accessible via @uref{http://gmane.org, Gmane} as
-@url{http://dir.gmane.org/gmane.lisp.scheme.geiser,
+@url{http://dir.gmane.org/@/gmane.lisp.scheme.geiser,
gmane.lisp.scheme.geiser}.
@item
@cindex bug tracker
You can submit bug reports either to the mailing list or to
-@uref{http://savannah.nongnu.org/bugs/?group=geiser, our bug tracker}
+@uref{http://savannah.nongnu.org/@/bugs/?group=geiser, our bug tracker}
over at Savannah.
@item
@cindex news feed
If you only need to hear about Geiser on new releases,
-@uref{http://savannah.nongnu.org/news/?group=geiser, the News page} and
-its @uref{https://savannah.nongnu.org/news/atom.php?group=geiser, Atom
+@uref{http://savannah.nongnu.org/@/news/?group=geiser, the News page} and
+its @uref{https://savannah.nongnu.org/@/news/atom.php?group=geiser, Atom
feed} are probably what you're looking for.
@item
@cindex IRC channel