This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-01
Channels
- # announcements (10)
- # asami (2)
- # babashka (10)
- # beginners (55)
- # biff (37)
- # calva (9)
- # cherry (1)
- # clj-kondo (11)
- # clojure (221)
- # clojure-bay-area (12)
- # clojure-europe (77)
- # clojure-hungary (3)
- # clojure-nl (5)
- # clojure-norway (12)
- # clojurescript (11)
- # cursive (1)
- # data-science (11)
- # emacs (27)
- # figwheel (3)
- # fulcro (11)
- # graphql (5)
- # helix (7)
- # honeysql (3)
- # humbleui (9)
- # interceptors (2)
- # introduce-yourself (2)
- # kaocha (12)
- # lsp (27)
- # malli (6)
- # nbb (70)
- # off-topic (6)
- # re-frame (6)
- # react (3)
- # reitit (9)
- # releases (2)
- # scittle (29)
- # shadow-cljs (26)
- # sql (13)
- # tools-deps (61)
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

However, it also breaks with coc-clojure @UEENNMX0T
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.
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
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)
Lol what the hell
it works for me. what do the logs say?
from clojure-lsp, I'm on head of master atm and they say result of definition is empty.
Ugh, sorry for breaking everyone's workflow. I'll keep poking and see what I can do
What's your coc config for clojure lsp?
maybe I can recreate that way?
I use coc's "release" branch and i use CocInstall to use coc-clojure, so i'm never ahead of everyone else
up to you! public might help others, but also notifies anyone who was unfortunate enough to comment lol
Indeed. I dont' mind reporting back once I have a conclusion...I'll pop over to you
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.
