Fork me on GitHub
#vim
<
2021-10-24
>
Hukka08:10:25

Uf, time to get back to nvim again after trying other options for a couple of months. But I think I'll still keep trying some new things, and see what's up with conjure and vim-iced having only ever used fireplace or custom scripts

Hukka08:10:17

What's the deal these days with LSP and neovim re clojure? Especially with conjure/iced? Use the neovim internal lsp for linting, autocompletion etc? Or CoC? Or iced plugins? Or just ALE?

walterl13:10:14

For me it's Conjure + coc.nvim + clojure-lsp. The latter is becoming more and more indispensable.

clojure-lsp 5
🚀 3
Ngoc Khuat09:10:20

I second this, Prefer conjure over fireplace because it has a whole log buffer and ability to paste last result

nate21:10:50

Me too. The trio of Conjure/CoC/Clojure-lsp is amazing and getting better at an incredible clip.

Aleksander21:10:12

what's CoC role in this setup? Is it purely autocompletion or it does more?

walterl21:10:43

It's also the LSP client that connects to clojure-lsp

ericdallo21:10:41

AFAIK CoC has most LSP features like completion, find defintion, references, call clojure-lsp refactors, code actions and probably more

walterl21:10:41

I'm not really too fond of CoC (it reinvents too many vim wheels), but it's the easiest to use atm (AFAIK)

walterl21:10:06

and the most feature complete

berkeleytrue21:10:18

Conjure/nvim-cmp/clojure-lsp/lspconfig for me.

walterl21:10:53

Does lspconfig allow you to use clojure-lsp's callHierarchy features? https://clojure-lsp.io/features/#call-hierarchy

berkeleytrue21:10:08

Not sure what that is. I'm afraid I don't use many advanced features past auto-import stuff.

berkeleytrue21:10:59

oh I see. That's pretty neat. I feel like you could configure that through nvim-cmp

Aleksander21:10:46

AFAIK, nvim-cmp only does autocompletion. You can get most LSP features like find defintion, references, call clojure-lsp refactors, code actions via inbuild vim-lsp, but from what I understand not callHierarchy