Clojurians Log v2
conjure
With the help of the Astrocommunity people the Clojure support for https://astronvim.com/ is much more flexible (and vanilla config by default), once https://github.com/AstroNvim/astrocommunity/pull/982 is merged Update: the PR was merged as I wrote this post 🙂
• conjure is now the multi-language 'code-runner' it really is and has its own config outside the Astrocommunity Clojure pack
• ts-comments.nvim has been updated to support the Clojure comment patterns
• nvim-parinfer & nvim-treesitter-sexp are now their own plugin configs
The Astrocommunity Clojure pack assembles all these Astrocommunity package configs, ensures Clojure Treesitter parser and Clojure LSP server is installed automatically. So Clojure support can be added with one configuration line.
Practicalli Neovim provides https://practical.li/neovim/configuration/astronvim/astrocommunity/, which is pretty easy (in my humble opinion).
I'll update https://practical.li/neovim/configuration/astronvim/ once the PR is merged.
Why do I get this error/warning in :checkhealth when trying practicalli/astronvim config (no this warning when using original astronvim config):
- ERROR Issues were reported when loading your specs:
- WARNING Two plugins with the same name and different url:
- WARNING {
- WARNING new = { "astronvim/astrocore",
- WARNING _ = {
- WARNING dep = false,
- WARNING fid = 180,
- WARNING fpid = 179,
- WARNING module = "astrocommunity.editing-support.vim-visual-multi"
- WARNING },
- WARNING dir = "/Users/me/.local/share/astronvim/lazy/astrocore",
- WARNING name = "astrocore",
- WARNING opts = ,
- WARNING url = ""
- WARNING },
- WARNING old = { "AstroNvim/astrocore",
- WARNING _ = {
- WARNING dep = false,
- WARNING fid = 172,
- WARNING fpid = 171,
- WARNING module = "astrocommunity.color.ccc-nvim", Perhaps it's due to the recent changes between AstroNvim V3 and V4. https://docs.astronvim.com/configuration/v4_migration/ I would need to know more about what was done and when. Or at least if a separate configuration directory was used. I'll also try check health and see if I can replicate the issue
Yes, I used a separate config directory ~/.config/astronvim and I also tried this:
mv ~/.local/share/nvim ~/.local/share/nvim.bak
mv ~/.local/state/nvim ~/.local/state/nvim.bak
mv ~/.cache/nvim ~/.cache/nvim.bakAnd I have my “normal” nvim config in ~/.config/nvim that uses Plug instead of Lazy.
I also tried
rm -rf ~/.local/share/astronvim
rm -rf ~/.local/state/astronvim
rm -rf ~/.cache/astronvim
rm -rf ~/.config/astronvimI found the cause. Its a bug in the https://github.com/AstroNvim/astrocommunity/blob/main/lua/astrocommunity/editing-support/vim-visual-multi/init.lua that the Practicalli config imports, in https://github.com/practicalli/astronvim-user-config/blob/main/lua/community.lua#L41`community.lua`https://github.com/practicalli/astronvim-user-config/blob/main/lua/community.lua#L41. This is why its not in the AstroNvim template.
I will submit a PR to fix the vim-visual-multi plugin config.
In the mean time, suggest commenting the vim-visual-multi import line in community.lua before running :help checkhealth . The checkhealth does run, although I am getting a few warnings, possibly due to using Neovim 0.10.0
The plugin seems to work fine even with this bug in the config
Once https://github.com/AstroNvim/astrocommunity/pull/992 has been merged then this issue should be resolved (It works locally and the other warnings have also disappeared) Thanks for helping me diagnose this issue.
Anyone else notice perchance that with the latest neovim (0.10.0) and Conjure they have to manually do set ft=clojure for conjure to kick in?
I've been setting the filetype to Clojure for about a year now, every since I moved to the lazy package manager (and AstroNvim). I usually set the filetype to all the conjure supported languages now.
Interesting. I have an autogroup that detects the filetype and sets it to clojure. I'll have to investigate later if it's stopped working correctly...or if it's something else.