This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-04
Channels
- # announcements (7)
- # aws (5)
- # babashka (72)
- # beginners (43)
- # calva (12)
- # cider (9)
- # clara (3)
- # clj-kondo (12)
- # cljdoc (32)
- # cljs-dev (10)
- # cljsrn (1)
- # clojure (78)
- # clojure-dev (50)
- # clojure-europe (17)
- # clojure-gamedev (8)
- # clojure-nl (1)
- # clojure-spec (30)
- # clojure-uk (3)
- # clojurescript (52)
- # core-async (1)
- # cursive (5)
- # datomic (8)
- # emacs (58)
- # events (2)
- # fulcro (5)
- # graalvm (7)
- # holy-lambda (37)
- # honeysql (9)
- # jobs (5)
- # leiningen (3)
- # lsp (7)
- # lumo (2)
- # malli (3)
- # meander (13)
- # membrane-term (64)
- # missionary (19)
- # music (3)
- # nextjournal (8)
- # off-topic (29)
- # pathom (16)
- # polylith (14)
- # portal (16)
- # re-frame (2)
- # reagent (5)
- # sci (14)
- # shadow-cljs (20)
- # spacemacs (6)
- # sql (1)
- # tools-deps (58)
- # vim (14)
is there a vim plugin to jump to the definition of a function within the file and across namespaces?
Other options I've used (before LSP) include vim-fireplace and Conjure. I believe both of those will use your connected nREPL to find the definition you're looking for.
I would love one that would get into java jar files haha
Me and @U04V15CAJ already discussed how that could work but it's kind of in hammock time though. I think adding support for find definition of java classes would be a incredible start
The big questions: • Bytecode vs source parsing or both • Where will you redirect to when you only have bytecode to inspect?
maybe we should start with the easiest, non byte code? not sure, I think cursive generate stubs
Yes, we could just start light weight using a doclet based thing like CIDER does perhaps.