slimv
asdf
slimv | asdf | |
---|---|---|
14 | 341 | |
450 | 20,547 | |
- | 1.1% | |
3.2 | 7.6 | |
10 months ago | 3 days ago | |
Common Lisp | Shell | |
- | MIT License |
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.
slimv
-
Does anyone use vim for lisp dev?
I use Vim with slimv, and have for years.
-
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.
-
From Common Lisp to Julia
https://GitHub.com/jpalardy/vim-slime is a terrible SLIME to be honest! It is not even a SLIME. It just This does not look like SLIME. It just copies text from one text buffer and paste it to another Vim buffer which is probably running a REPL. "Probably" because who knows what the target buffer is running. vim-slime does not care. This is not Superior Lisp Interaction Mode for $EDITOR (SLIME) in any way.
vim-slime does not connect to any Swank server. It does not understanding Lisp s-expressions. It would happily copy any random text into any random REPL and call it job done! Lisp interaction mode is much much more than just copying and pasting text around. A superior lisp interaction mode gives you live debugging, handling conditions, inspecting variables, navigating the stack frames, ... Vim-slime cannot do anything like this because, well, it just copy-pastes stuff around. Vim-slime is a disingenious and misleading name for a project that is not SLIME.
If you really want to use Vim, do yourself a favor and use https://github.com/kovisoft/slimv and experience a true Lisp interaction mode.
-
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
-
Is SLIME setup possible for Vim?
I've seen SLIMV recommended as a SLIME alternative for Vim. Like SLIME, SLIMV is a SWANK client.
- Slimv – Superior Lisp Interaction Mode for Vim (“Slime for Vim”)
-
What would you consider a modern lisp workflow/toolchain?
I found Vlime to be more updated than slimv and give a smoother experience. With time I've switched to bare neoterm which I highly recommend. CL and lisps in general are designed with a text repl in mind, so this is the method that is guaranteed to work on every obscure CL distribution, and also transfer well to any other REPL-based languages.
-
Opening and running functions in Portacle
If you are already familiar with vim you may want to use slimv
-
Is anyone programming in lisp?
You need Parinfer. Several versions are available for Vim. It's easier to learn than Paredit and works better with Vim-style editing anyway. Lisp emphasizes interactivity with the REPL. It helps if you can send forms you're editing to the REPL for testing. Try something like slimv.
asdf
-
Install Asdf: One Runtime Manager to Rule All Dev Environments
The main issue most people have with asdf is that it’s annoyingly slow. Not unusably so, but just enough that it’s irritating.
I identified [0] the source for much of it (sub-shells and pipes) and began a PR [1], but became bogged down with BATS testing, and then found mise / rtx, so kind of lost interest. Sorry. You can always implement these if you’d like.
[0]: https://github.com/asdf-vm/asdf/issues/290#issuecomment-1383...
[1]: https://github.com/asdf-vm/asdf/pull/1441
- Show HN: I made a multiple runtime version manager that can be used on Windows
-
Volta – Fastest Node version manager in Rust
Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions
https://asdf-vm.com/
-
Pyenv – lets you easily switch between multiple versions of Python
Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?
These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…
We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.
-
A Journey to Find an Ultimate Development Environment
The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).
-
How to Install Your Python Version on Ubuntu
(asdf)[https://asdf-vm.com/] fully supports Python and almost any other language. I've been using it for Ruby, Python, Elixir, and other languages for years and never looked back.
-
Beginners Intro to Trunk Based Development
Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).
-
Practical Guide to Trunk Based Development
There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:
- Criando seu ambiente com ASDF
-
Kotlin version manager
I've really been enjoying asdf, which is a program that allows you to install specified versions of dev utilities as well as dynamically manage them via shims and .tool-versions files.
What are some alternatives?
vlime - A Common Lisp dev environment for Vim (and Neovim)
SDKMan - The SDKMAN! Command Line Interface
w3m.vim - w3m plugin for vim
pyenv - Simple Python version management
paredit.vim - Paredit Mode: Structured Editing of Lisp S-expressions
rbenv - Manage your app's Ruby environment
vim-sexp-mappings-for-regular-people - vim-sexp mappings for regular people
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
volta - Volta: JS Toolchains as Code. ⚡
awesome-cl - A curated list of awesome Common Lisp frameworks, libraries and other shiny stuff.
HomeBrew - 🍺 The missing package manager for macOS (or Linux)