slime VS qlot

Try https://github.com/slime/slime/commit/e6a71c725c8e13d7d4c40e6a6fa7b696575a8d01

With emacs your two choices are either SLIME or SLY. Slime is a good place to start - it's rock solid. Once you get moving you can make a judgement call on whether or not SLY has features you'd like over what SLIME has available.

To provide a bit more context, most of SLIME is just Common Lisp code (https://github.com/slime/slime), with a bunch of Emacs Lisp code alongside to support interfacing with Emacs. But you don't need that Emacs Lisp code to take advantage of almost all of the functionality SLIME provides. For instance, if you want to know who-calls a function, there's some command in emacs to do it, but all that command is doing is just a bit of elisp code which sends a message to Swank (a server running inside Common Lisp) and Swank invokes some native CL code to figure that out and return the results, then finally a bit of elisp code presents the results in some way. Vim can do the same thing just fine with vimscript/python (what the Slimv plugin uses) or otherwise, the bulk of the work in figuring out the list of callers of some function is done by the CL code (and CL implementation itself).

SLIME or SLY for Common Lisp (if you want to work with it), Geiser for various Schemes

That's rather new, https://github.com/slime/slime/commit/789584a7acb15747678fa62a8fcfc8d1187be867 is probably about that.

With that headline on HN, I was expecting this: https://common-lisp.net/project/slime/

SLIME or Sly for Common Lisp, Geiser for most Scheme implementations, or racket-mode for Racket?

For example, some people that are Common Lisp programmers, but don't use GNU Emacs, may decide to use GNU Emacs because of the slime-mode workflow.

Other options are:

- Quicklisp -really slick, libraries in there are curated. (with https support here: https://github.com/rudolfochrist/ql-https and here: https://github.com/snmsts/quicklisp-https.git)

- for project-local dependencies like virtualenv: https://github.com/fukamachi/qlot

- a new, more traditional one: https://www.clpm.dev (CLPM comes as a pre-built binary, supports HTTPS by default, supports installing multiple package versions, supports versioned systems, and more)

For recent Quicklisp upgrades: http://ultralisp.org/

Ocicl is very new (5 days) and tries a new approach, building "on tools from the world of containers".

I frequently use roswell (and occasionally qlot) to manage my CL distributions and packages. Native support for roswell would be fantastic!

An easy example would be to look at qlot.asd.

I think definitely some kind of integration with quicklisp and/or qlot would be amazing, so you can open a project and have all the dependencies pulled and ready for your project.

I prefer to use Qlot.