From 0b961d9e5faf67db9c69b5175a443a6c9f17cca4 Mon Sep 17 00:00:00 2001 From: Andrew Sackville-West Date: Sat, 1 Jul 2017 15:31:48 -0700 Subject: fix broken links to incremental REPL references --- doc/parens.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/parens.texi b/doc/parens.texi index 9b146e9..f4f44f8 100644 --- a/doc/parens.texi +++ b/doc/parens.texi @@ -429,11 +429,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 -my opinion}, those are limitations we lispers are aware of, and they +@uref{http://programming-musings.org/2009/03/29/from-my-cold-prying-hands/index.html, +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-the-one-in-emacs.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. -- cgit v1.2.3