3 ms·
Link did not work, maybe this was meant? https://mov.im/?blog/phoe%40movim.eu/detecting-non-local-exits-in-common-lisp-2QAoHy https://mov.im/?blog/phoe%40movim
by pfdietz 5y ago
Link did not work, maybe this was meant?
https://mov.im/?blog/phoe%40movim.eu/detecting-non-local-exits-in-common-lisp-2QAoHy https://mov.im/?blog/phoe%40movim.eu/detecting-non-local-exi...
- dang 5y agoIt's because mov.im is giving us a 302 with redirect to https://mov.im/?notfound https://mov.im/?notfound. Does anybody know if this is intentional? or who we can get in touch with to fix this? The same problem happened with https://news.ycombinator.com/item?id=29891523 https://news.ycombinator.com/item?id=29891523 too. These are good posts, and I'd like to fix this problem.
- CapitalistCartr 5y agoI followed a link from http://planet.lisp.org/ http://planet.lisp.org/ to it, which still works. When I posted this, I tested the link (of course) and it worked for me, but now it doesn't. Edit: If I cut and paste the link from Planet Lisp, it works, but from here, they don't like us.