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.
info.vim
Posts with mentions or reviews of info.vim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-28.
-
vimscript over lua
As for writing plugins though, Lua beats Vim script any time of the day. I wrote info.vim back in the early days and it was a major pain to write in Vim script. If I had to redo it today I would 100% write it in Lua.
-
plugin annoncement - nvlime
Yeah, mapping a function instead of a mapping is even better. I just don't like if a predefined mapping is hard to remember or (even worse) conflicts with one of my existing mappings. Personally I like it the way Neovim's LSP client does it: you get a Lua (or Vim script) API that you can map yourself. In my info.vim I provide the commands :InfoNext, :InfoPrev and :InfoUp, but I also have a code snippet of reasonable default bindings in my README that people can just copy-past into their configuration. If they disagree with my defaults they can then change that snippet instead of having to fight my plugin to scrub away the defaults.
-
sidebar.nvim - A generic and modular lua sidebar
info.vim (my own)
-
Man pages in color, with links
I think we're all aware of the Man plugin, What I really want is info.vim being distributed by default aswell.
-
Future plans for Autotools
A wiki is not adequate documentation and I hate this trend of making documentation HTML only. Not everyone uses or even can use a web browser. GNU software has this great tool called Texinfo which lets you write a proper book-sized documentation with proper table of contents, chapters, and indexes. You can generate HTML, PDF, and most importantly info files. You can read info files in your terminal, in Emacs, or even in Vim (wrote a plugin for that).
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.
What are some alternatives?
When comparing info.vim and vlime you can also consider the following projects:
vinfo - Vim info documentation reader, lets you read info pages within Vim or start it from the shell prompt (instead of Info)
slimv - Official mirror of Slimv versions released on vim.org
sidebar.nvim - A generic and modular lua sidebar for Neovim
Vim - The official Vim repository
paredit.vim - Paredit Mode: Structured Editing of Lisp S-expressions
neovim - Vim-fork focused on extensibility and usability
nvim-metals - A Metals plugin for Neovim
nvlime - A Common Lisp development environment for Neovim
vim-dirvish - Directory viewer for Vim :zap: