IMHO a very well-written article with great attention to detail. I
especially liked the section on paredit with its step-by-step
I wonder why the author doesn't mention the plugin vim-slime, given that
it seems to be more popular than either Slimv or Vlime on GitHub. From
what I can gather, Slimv and Vlime are more focused on Lisp with
built-in completion and debugging whereas vim-slime is language agnostic
and simply recreates just the "connected REPL" behavior of Slime.
The "vim-slime" plugin is not appropriate for my blog post because it is
nothing like SLIME. In fact, the word "slime" in "vim-slime" is poorly
chosen. It supports none of the SLIME features. It does not even provide
the "connected REPL" experience like SLIME, Slimv, or Vlime does. Here
are the major reasons why vim-slime is very limited and insufficient as
a Lisp development environment when compared to SLIME, Slimv, or Vlime:
Swank server is an integral component of SLIME. It is essential to the
way SLIME works. A plugin that does not talk to Swank server can hardly
be anything like SLIME. Slimv and Vlime on the other hand talk to the
same Swank server that SLIME talks to. Slimv and Vlime are
re-implementations of the client component of SLIME. They send SLIME
commands to Swank just like SLIME does. As a result, Slimv and Vlime are
able to support a good portion of the features available in SLIME.
Thank you for the explanation.
Such a great article.
I really wish though there is a button to turn on and off so one can
read only about Slimv or Vlime or both.
This is great! I just recently started using Vlime and had been
starting SBCL externally but
your \rr hotkey has just saved me
lots of annoyance!
Same with the interactive debugging, I didn't know you could inspect
the call stack like that and evaluate stuff! I only knew about
choosing restarts. Thanks for this write up!