3 ms·

Lisp in Vim (2019)

88 points by whent 4mo ago

lawn 4mo ago
I've been using Fennel to write my Neovim configurations and it's been really nice. The setup is a bit annoying but once there it's pretty nice. Some details about my setup (although I've moved back to lazy.nvim instead of vim.pack): https://www.jonashietala.se/blog/2025/10/29/packing_neovim_with_fennel/ https://www.jonashietala.se/blog/2025/10/29/packing_neovim_w...
- c-hendricks 4mo ago
  Curious why you went back to lazy.nvim? I had to write some stuff to get some kind of lazy loading (now have "immediate", "vim.schedule", and "VimEnter + vim.schedule" lazy modes), plugin specs / setup functions are colocated, and using vim.packs unused `data` for config merging and it works well enough. Also, your treesitter auto install makes a common mistake: vim file type and treesitter grammar names don't match up. IE a .tsx file has a vim filetype of `typescriptreact` while the treesitter parser is named "tsx". You'll need something like this https://github.com/nvim-lua/kickstart.nvim/blob/cfdc17be3ae1607d4427332de0b29d556f9dda13/init.lua#L926 https://github.com/nvim-lua/kickstart.nvim/blob/cfdc17be3ae1..., and there's still the note that the `vim.treesitter.language.get_lang` call isn't really doing anything, since that function returns whatever is passed in if no parser matching the name has been registered. So that check is moot.
  - lawn 4mo ago
    Cool, thank you. I had some bugs with moving between a laptop and desktop and pack's lockfile kept getting out of sync, and pack didn't handle it well and sometimes even crashed. My build script also sometimes didn't work properly. I just got tired of dealing with it so I went back to lazy.nvim as it just works and does what I need.
    - c-hendricks 4mo ago
      Can't argue with that. Since switching to vim.pack I still feel like lazy.nvim loaded faster, but the less my config relies on folke the better (nothing against them personally, I just don't want to go months without bug fixes for all the plugins they maintain)
ARandomerDude 4mo ago
These days Conjure is the best way to write a lisp language in Neovim, in my opinion. It supports Clojure, Common Lisp, Fennel, etc. Not my project but I’m very thankful for those who contribute! https://github.com/Olical/conjure https://github.com/Olical/conjure
ChrisArchitect 4mo ago
Previously: 2019 https://news.ycombinator.com/item?id=21735148 https://news.ycombinator.com/item?id=21735148 2021 https://news.ycombinator.com/item?id=29612209 https://news.ycombinator.com/item?id=29612209 2024 https://news.ycombinator.com/item?id=39478441 https://news.ycombinator.com/item?id=39478441
busfahrer 4mo ago
Having only dabbled in Lisp and knowing nothing about the plugins TFA mentions, there's also this FWIW: https://github.com/jpalardy/vim-slime https://github.com/jpalardy/vim-slime

Lisp in Vim (2019)

88 points by whent 4mo ago

lawn 4mo ago

I've been using Fennel to write my Neovim configurations and it's been really nice. The setup is a bit annoying but once there it's pretty nice. Some details about my setup (although I've moved back to lazy.nvim instead of vim.pack): https://www.jonashietala.se/blog/2025/10/29/packing_neovim_with_fennel/ https://www.jonashietala.se/blog/2025/10/29/packing_neovim_w...

c-hendricks 4mo ago
Curious why you went back to lazy.nvim? I had to write some stuff to get some kind of lazy loading (now have "immediate", "vim.schedule", and "VimEnter + vim.schedule" lazy modes), plugin specs / setup functions are colocated, and using vim.packs unused `data` for config merging and it works well enough. Also, your treesitter auto install makes a common mistake: vim file type and treesitter grammar names don't match up. IE a .tsx file has a vim filetype of `typescriptreact` while the treesitter parser is named "tsx". You'll need something like this https://github.com/nvim-lua/kickstart.nvim/blob/cfdc17be3ae1607d4427332de0b29d556f9dda13/init.lua#L926 https://github.com/nvim-lua/kickstart.nvim/blob/cfdc17be3ae1..., and there's still the note that the `vim.treesitter.language.get_lang` call isn't really doing anything, since that function returns whatever is passed in if no parser matching the name has been registered. So that check is moot.
- lawn 4mo ago
  Cool, thank you. I had some bugs with moving between a laptop and desktop and pack's lockfile kept getting out of sync, and pack didn't handle it well and sometimes even crashed. My build script also sometimes didn't work properly. I just got tired of dealing with it so I went back to lazy.nvim as it just works and does what I need.
  - c-hendricks 4mo ago
    Can't argue with that. Since switching to vim.pack I still feel like lazy.nvim loaded faster, but the less my config relies on folke the better (nothing against them personally, I just don't want to go months without bug fixes for all the plugins they maintain)

ARandomerDude 4mo ago

These days Conjure is the best way to write a lisp language in Neovim, in my opinion. It supports Clojure, Common Lisp, Fennel, etc. Not my project but I’m very thankful for those who contribute! https://github.com/Olical/conjure https://github.com/Olical/conjure

ChrisArchitect 4mo ago

Previously: 2019 https://news.ycombinator.com/item?id=21735148 https://news.ycombinator.com/item?id=21735148 2021 https://news.ycombinator.com/item?id=29612209 https://news.ycombinator.com/item?id=29612209 2024 https://news.ycombinator.com/item?id=39478441 https://news.ycombinator.com/item?id=39478441

busfahrer 4mo ago

Having only dabbled in Lisp and knowing nothing about the plugins TFA mentions, there's also this FWIW: https://github.com/jpalardy/vim-slime https://github.com/jpalardy/vim-slime