Fork me on GitHub
#lsp
<
2022-11-01
>
dharrigan17:11:53

sigh - anyone else using neovim + coc + lsp - it seems that goto definition (on an included depdenceny) is broken (again) - but this time I think it's coc

ohno 1
sheluchin17:11:46

coc seems to get breaking changes quite often.

dharrigan17:11:05

Anyhoo, I've narrowed it down (git bisect ftw)

dharrigan17:11:31

It seems that from commit 648db91d258bbb70b6c02f8759a644692893dc41 it breaks.

👍 1
dharrigan17:11:41

However, it also breaks with coc-clojure @UEENNMX0T

sheluchin17:11:54

I've been thinking of moving to the built in neovim lsp instead. Just haven't had the time to give it a go yet.

dharrigan17:11:02

as in, if I use v0.0.9 of coc-clojure, it works with the previous commit, using v0.0.10 it does not work

dharrigan17:11:28

it's a combination of two things - coc and coc-clojure

dharrigan17:11:04

coc.nvim @ce2eaea1 + coc-clojure @v0.0.10 = doesn't work

dharrigan17:11:59

coc.nvim @ce2eaea1 + coc-clojure @v0.0.9 = works

dharrigan17:11:36

coc.nvim @648db91d + coc-clojure @v0.0.9 = does not work

dharrigan17:11:46

(anything from @648db91d doesn't work)

dharrigan17:11:05

Do you see the same @UEENNMX0T with latest coc and latest coc-clojure, are you able to go-to-defintion on a included library (not your repo source code)

Noah Bogart18:11:40

Lol what the hell

Noah Bogart19:11:07

it works for me. what do the logs say?

dharrigan20:11:10

from clojure-lsp, I'm on head of master atm and they say result of definition is empty.

Noah Bogart20:11:36

Ugh, sorry for breaking everyone's workflow. I'll keep poking and see what I can do

dharrigan20:11:57

it may not be you 🙂 It may be a combination of a few things

Noah Bogart20:11:28

What's your coc config for clojure lsp?

Noah Bogart20:11:34

maybe I can recreate that way?

Noah Bogart20:11:02

I use coc's "release" branch and i use CocInstall to use coc-clojure, so i'm never ahead of everyone else

dharrigan20:11:37

Do you want to continue on this thread, or talk via DM?

Noah Bogart20:11:10

up to you! public might help others, but also notifies anyone who was unfortunate enough to comment lol

dharrigan20:11:30

Indeed. I dont' mind reporting back once I have a conclusion...I'll pop over to you

dharrigan05:11:31

Reporting back. Thanks to the great investigatory work by @UEENNMX0T, the issue has been fixed. Upgrading to the latest version of coc-clojure, i.e., 0.0.13, resolves the problem.

1
❤️ 1
thanks3 1