Re:How to write Common Lisp in 2017 – an initiation manual
by Grue3 on Tuesday March 28, 2017 @06:10PM
(#13981223)
Everything should Just Work (TM) on Windows these days. SBCL provides reasonably fresh binaries to download. Quicklisp can be installed by entering the necessary commands into SBCL console. Emacs has a Windows installer. SLIME can be installed from Quicklisp. And so on. I develop in Lisp on both Windows and Linux machines, it works exactly the same (which cannot be said of some other languages).
Re:How to write Common Lisp in 2017 – an initiation manual
by aidenn0 on Tuesday March 28, 2017 @06:11PM
(#13981231)
Portacle[1] and lispstick[2] both provide portable sbcl-based development environments on windows.
Quicklisp is really simple to track what it's doing, and trivial to manage multiple installs of quicklisp simultaneously (though you can only use one install at a time in a given lisp image). Everything goes in <install-directory>/dists/<distribution-name>.
1: https://shinmera.github.io/portacle/
2: https://github.com/jasom/lispstick-automate/releases/tag/1.0
Re:How to write Common Lisp in 2017 – an initiation manual
by orthecreedence on Tuesday March 28, 2017 @05:24PM
(#13980863)
I've been telling people for years to just use Clozure CL on windows. It might be a bit slower, but it's still blazing fast and you don't have to deal with compatibility issues.
Re:How to write Common Lisp in 2017 – an initiation manual
by baggers on Wednesday March 29, 2017 @07:26AM
(#13985049)
The video in question: https://www.youtube.com/watch?v=VnWVu8VVDbI&t=744s
As aidenn0 mentioned portacle will hopefully be a good option for some when finished as it gives you a complete environment in one shot.
For installing CL I may update my video to use Roswell at some point, I've been having good success with it when using TravisCI.
Watch YouTube video from Baggers. It's a lot more complicated than your average windows user will want to go through. Than you have to setup EMACS, quicklisp...etc. I never really new what quicklisp was doing and it made me nervous (I trust VS nuget).