summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2020-06-26 22:23:51 +0100
committerJose Antonio Ortega Ruiz <jao@gnu.org>2020-06-26 22:23:51 +0100
commit3d2062779ec91bbd702ed0d290630067f305d841 (patch)
treeb21868bdb2030bd48610de4d158f8a470d608f54
parent4835112569a3d093c7b2322af5312a8b4c59061b (diff)
downloadgeiser-3d2062779ec91bbd702ed0d290630067f305d841.tar.gz
geiser-3d2062779ec91bbd702ed0d290630067f305d841.tar.bz2
Links to olde blog posts
Thanks to Sebastian, who noted this in issue #314
-rw-r--r--doc/parens.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/parens.texi b/doc/parens.texi
index 55a23f7..118c020 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://jaortega.wordpress.com/2009/03/29/from-my-cold-prying-hands/index.html,
+@uref{https://jaortega.wordpress.com/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-the-one-in-emacs.html,
+@uref{https://blog.racket-lang.org/2009/03/the-drscheme-repl-isnt-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. Moreover, you can invoke