SLIMA
Superior Lisp Interactive Mode for Pulsar (by neil-lindquist)
vlime
A Common Lisp dev environment for Vim (and Neovim) (by vlime)
| SLIMA | vlime | |
|---|---|---|
| 4 | 15 | |
| 62 | 417 | |
| - | 0.7% | |
| 3.6 | 5.4 | |
| 10 months ago | 7 months ago | |
| CoffeeScript | Vim Script | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SLIMA
Posts with mentions or reviews of SLIMA.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-15.
-
What is to go-to environment on Windows for Common LISP development?
Careful! The Atom plugin is SLIMA, since a few years: https://github.com/neil-lindquist/SLIMA/ (it's a fork, atom-slime's maintainer didn't feel like sharing commit rights). In doubt: https://lispcookbook.github.io/cl-cookbook/editor-support.html
-
Slima for Atom: Quote doesn't evaluate properly
https://github.com/neil-lindquist/SLIMA/issues would probably like to know about that.
- Hell Is Other REPLs
-
VS Code
You can also change to Atom and use SLIMA ( https://github.com/neil-lindquist/SLIMA ), which may offer an easier transition than VS Code -> Emacs.
vlime
Posts with mentions or reviews of vlime.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-08.
-
Does anyone use vim for lisp dev?
https://github.com/vlime/vlime works for me fine
-
Developing Common Lisp using GNU Screen, Rlwrap, and Vim
You should try out Vlime, it is a bit janky but it beats copy-pasting into a terminal any day.
-
Portacle - Does it have auto indent?
Maybe you should stick to one new thing at a time. Vim is more than capable of handling Common Lisp. Look at Slimv and Vlime for vim-style SLIME. Focus on CL first. You can come back to Doom / Emacs later.
-
What is to go-to environment on Windows for Common LISP development?
Neovim works just fine. I use Neoterm to send-to-repl, here's what my config looks like. Your other options include vlime and slimv. I switched to neoterm because it's simple, explicit, and doesn't create unpredictable windows. Works for any other language just as well.
- Why Lisp?
-
Are there plugins for Neovim that don't exist, that should exist, in your opinion?
A proper Neovim client for Slime or Sly. The closest is Vlime, but its UI is really janky.
-
Common Lisp vs Racket
Join me vim brother and don't settle for forcing yourself to use emacs while developing in CL when you don't have to! You even have two vim options! https://github.com/kovisoft/slimv and https://github.com/vlime/vlime with a great comparison of the two: https://susam.net/blog/lisp-in-vim.html
-
Lisp programming configuration for neovim
If you're interested more in Common Lisp, there's both vlime and vim-slime however I don't have any experience with them.
-
Noob looking to learn Vim on Windows for writing/programming/notes
I think I'll dig at vimtutor within a few days, then. I've seen it mentioned a few times already, so now's a good time I reckon. Like you said, I'll be avoiding plugins, but with the guide I referenced, vlime is mentioned. You don't think that'll be too problematic on Windows, do you? I recall seeing that plenty of plugins don't work outside of linux. Thanks again, btw!
-
What would you consider a modern lisp workflow/toolchain?
That's quite a tough question because different people appreciate different things about Emacs. Personally I use Neovim as my text editor with Vlime for live Common Lisp integration (works with Vim as well). Vlime uses the same backend as Slime for Emacs, so the features should be the same, even if the interface is different. I know there is also Slima for Atom, but I have never used Atom, so no idea how well it works.