This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # announcements (8)
- # babashka (6)
- # beginners (70)
- # bristol-clojurians (1)
- # chlorine-clover (15)
- # cider (3)
- # cljs-dev (2)
- # cljsrn (27)
- # clojure (249)
- # clojure-europe (19)
- # clojure-italy (2)
- # clojure-nl (12)
- # clojure-spec (11)
- # clojure-uk (42)
- # clojuredesign-podcast (6)
- # clojurescript (39)
- # community-development (1)
- # conjure (43)
- # cursive (37)
- # data-science (1)
- # datomic (3)
- # duct (16)
- # figwheel-main (23)
- # fulcro (3)
- # instaparse (5)
- # java (5)
- # jobs (1)
- # jobs-discuss (1)
- # malli (11)
- # off-topic (27)
- # re-frame (32)
- # reagent (5)
- # reitit (2)
- # rum (15)
- # shadow-cljs (24)
- # spacemacs (7)
- # sql (5)
- # test-check (3)
- # tools-deps (5)
It would be nice if the Clojure-specific constants like
##Inf would appear in the auto-completion list.
I haven't been able to evaluate expressions in Cursive for a while (when stopping at a break point). Is there a solution for that?
You can set a break-point for one thread only instead of for all. But eval expression (alt-f8) should work even though there are some limitations.
@U1G0HH87L That is https://github.com/cursive-ide/cursive/issues/2345, which should be fixed in Cursive 1.9.2.
Trying to create a new Remote Clojure REPL configuration but seeing this error "No modules containing clojure.main found"....any ideas?
hmm....i see these in the event log
11:43 AM Dependency resolution error Error synchronising /Users/michaelcohen/xbeam/muncher/project.clj: Failed to collect dependencies at lein-ancient:lein-ancient:jar:0.6.15 11:43 AM Dependency resolution error Error synchronising muncher:0.1.0-SNAPSHOT: Failed to collect dependencies at amazonica:amazonica:jar:0.3.152
yeah, that seems a like a problem that can cause this kind project/module related issues.
if you cannot find the leiningen tool window or it’s empty, you may have to re-import the project as a leiningen project: https://cursive-ide.com/userguide/leiningen.html
so your project was correctly recognized as of type leiningen... what happens if your hit the refresh button at the top?
it does appear to error. it pops open another message in the event log in the bottom right corner. which is strange, because....
yeah, we used it before but quickly switched to cognitect-labs aws-api and never looked back...
one more thing to try is the good ol', ultimate weapon: "Invalidate Caches / Restart"
FWIW, i had to remove the
:local-repo key from
project.clj and then Cursive picked everything up just fine
@U015YDZ16AJ Just to make sure I understand, using
:local-repo broke the Cursive project resolution, is that right? What did you have that set to?
:local-repo was just set to a directory in the root of the project. all of the jars had already been downloaded there by maven. first i removed amazonica, which was the very first dep in this project, then tried to start a repl, got the same error that the next dep couldn't be resolved. removed that one, got the error again with the new, first dep in
project.clj , finally just removed
:local-repoand then it resolved everything...
I've got the same error today, in existing project, using deps.edn project. Any solutions?