slimv
fructure
slimv | fructure | |
---|---|---|
14 | 8 | |
450 | 443 | |
- | - | |
3.2 | 3.7 | |
10 months ago | 3 months ago | |
Common Lisp | Racket | |
- | Apache License 2.0 |
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.
fructure
-
Racket: The Lisp for the Modern Day
Even the racket teachpack libraries designed for education are very capable; I was able to make this structured editor with only using teachpack content without external deps: https://github.com/disconcision/fructure
-
Common Lisp vs Racket
Right, it's fine, and is a pretty basic macro. Doubly linked lists are pretty basic data structures too, even the Rust versions once you figure it out. I like your sibling comment making it look like the CL version. I still want to know in more detail though why you think that doing things this way instead of the CL way is less likely to be "fragile and break down" for the complicated stuff, it would help to have a specific complicated example to showcase. Perhaps the linked https://github.com/disconcision/fructure in another comment would be a good study? The author there claimed they might not have been able to manage with defmacro, maybe someone familiar with both could articulate the challenges in detail. Is it just an issue of some things benefit a lot from pattern matching, and if so, does using CL's Trivia system mitigate that at all (in the same way that using gensym+packages+Lisp-2ness can mitigate hygiene issues)?
- Fructure: A structured interaction engine in Racket
-
graph-based UI for Lisp/Scheme
see also: fructure
- Why text only.
- An Intuition for Lisp Syntax
What are some alternatives?
vlime - A Common Lisp dev environment for Vim (and Neovim)
LIBUCL - Universal configuration library parser
w3m.vim - w3m plugin for vim
paredit.vim - Paredit Mode: Structured Editing of Lisp S-expressions
cmu-infix - Updated infix.cl of the CMU AI repository, originally written by Mark Kantrowitz
vim-sexp-mappings-for-regular-people - vim-sexp mappings for regular people
coherence - Oracle Coherence Community Edition
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
slime - The Superior Lisp Interaction Mode for Emacs
awesome-cl - A curated list of awesome Common Lisp frameworks, libraries and other shiny stuff.
racket-binfmt - A binary format parser generator DSL with support for limited context-sensitivity.