Fork me on GitHub
#vim
<
2021-02-27
>
orestis19:02:02

Oh man I've finally gotten around to install LSP and TreeSitter, and my head is spinning... TreeSitter not so much (unless I'm missing something) but LSP is huge...

orestis19:02:55

yes, that's my saturday night 😛

mynomoto19:02:54

lsp is amazing.

futurile21:02:26

what's the value over CoC? I haven't installed vim-lsp as I couldn't work out what additional value it would provide

futurile21:02:11

I'm getting completion from CoC, and then vim-iced gives me docs. So I guess I couldn't figure out what the real addition__ would be! :-)

orestis08:03:13

I haven't used CoC -- the Node.js and the VSCode references put me off. The built in LSP in Neovim works without any real need for plugins, which is always nice.

orestis08:03:25

It would be good to share some screenshots of what our setups look like though 🙂

mynomoto19:03:59

Yeah, I misunderstood the original message, I use clojure-lsp via CoC, never tried the built in one. I think you need nvim 0.5 for that.

yiorgos14:03:58

Is treesitter available only for neovim at the moment? I can’t find anything for vim

orestis08:03:36

Treesitter is NeoVim only

👍 3
practicalli-john09:03:39

I do encourage people to share the specifics of what they find useful with LSP. People share their excitement about LSP, but it's hard to understand why without very specific examples.

orestis11:03:06

It’s essentially a static analysis toolkit that plugs into your favorite editor. So I get jump to definition, documentation, auto-completion, find references etc without needing REPL, which means ClojureScript support works very nicely.

orestis11:03:34

And I’m using the same backend process as VSCode and Emacs so a rising tide lifts my boat too