This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-31
Channels
- # announcements (6)
- # babashka (40)
- # beginners (6)
- # calva (1)
- # cider (1)
- # clerk (43)
- # clj-kondo (3)
- # clojure (93)
- # clojure-denver (8)
- # clojure-europe (52)
- # clojure-norway (20)
- # clojure-sweden (7)
- # community-development (5)
- # datascript (15)
- # datomic (30)
- # emacs (24)
- # events (15)
- # fulcro (23)
- # graalvm (12)
- # gratitude (1)
- # helix (4)
- # honeysql (4)
- # hoplon (39)
- # hyperfiddle (7)
- # introduce-yourself (1)
- # jobs (1)
- # jobs-discuss (26)
- # lambdaisland (3)
- # lsp (6)
- # matcher-combinators (2)
- # matrix (5)
- # meander (39)
- # nrepl (4)
- # nyc (1)
- # off-topic (5)
- # portal (73)
- # practicalli (1)
- # re-frame (2)
- # reitit (22)
- # releases (1)
- # remote-jobs (4)
- # shadow-cljs (5)
- # sql (17)
- # testing (1)
- # tools-deps (15)
I was working on https://github.com/borkdude/edamame earlier and ran into a silly bug where I'd try to go from one namespace to another, and vim (relying on clojure-lsp data) would take me to the jar of my local .m2
copy of edamame. the deps.edn
file doesn't have the library, but i have clojure-lsp running separately in a wholly different vim instance in a library that does use edamame. has anyone run into this before?
I have run into this before yes and also reported a few times. This happened to me with babashka.cli, if you search for that in this channel you might find it
cool, thanks
Not sure I get the issue, but one instance of clojure-lsp has nothing with other in other project, could you explain what you did so I can try to repro?
well, i can't seem to reproduce it now lol, so forgive me. i'm not entirely sure what I did wrong. but when i called cursor-info
on the edamame.impl.parser
symbol in the edamame.core
namespace declaration, it said it was in reference to the jar and not to the file