This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-11
Channels
- # announcements (6)
- # babashka (7)
- # beginners (145)
- # biff (2)
- # calva (9)
- # cider (4)
- # circleci (9)
- # clj-commons (22)
- # clj-kondo (26)
- # cljs-dev (70)
- # cljsrn (4)
- # clojure (46)
- # clojure-australia (9)
- # clojure-europe (62)
- # clojure-nl (5)
- # clojure-norway (4)
- # clojure-spec (11)
- # clojure-uk (3)
- # clojurescript (18)
- # copenhagen-clojurians (1)
- # core-async (1)
- # cursive (13)
- # datahike (6)
- # datomic (47)
- # emacs (5)
- # events (2)
- # fulcro (13)
- # google-cloud (2)
- # gratitude (2)
- # helix (5)
- # honeysql (5)
- # hyperfiddle (31)
- # jobs (1)
- # jobs-discuss (6)
- # london-clojurians (1)
- # lsp (5)
- # off-topic (9)
- # polylith (12)
- # portal (18)
- # re-frame (5)
- # reagent (29)
- # releases (2)
- # shadow-cljs (43)
- # specter (1)
- # test-check (8)
- # vim (1)
- # xtdb (66)
We're seeing behaviour where if there is a long running process in the REPL (particularly if it's attempting to connect to some remote and and waiting for a timeout), IntelliJ as a whole seems to lock up. Specifically the terminal built into IntelliJ stops accepting input. Is this a known issue?
No, I haven't experienced this before. I've had things run for over 10 minutes but I don't know what kind of "long" you mean
We have a monorepo tools.deps project where each sub-project is loaded as a module in Cursive. As an example, Module A uses functions from Module B. But “Find usages” on a function in Module B does not find usages in Module A, only internally in Module B. Is this supposed to work across modules?
https://github.com/cursive-ide/cursive/issues/2554 whether or not it is, it is probably related to the cause of the linked issue and the workaround could be similar
Not polylith. And sorry, forgot to mention one important fact: Module B is a dependency of Module A by using :local/root
. I suppose that’s the main reason, that Module A knows how to find Module B, but not the other way around.
Yes, dependencies normally only work in one direction. Is there a reason code in B should be able to access A?
To more concrete, we have an “app” module and a “lib” module. app depends on lib via :local/root. When doing find usages on a function in lib, it only shows other uses in lib, not the uses in app
Not polylith. And sorry, forgot to mention one important fact: Module B is a dependency of Module A by using :local/root
. I suppose that’s the main reason, that Module A knows how to find Module B, but not the other way around.