Is there a way to disable the Run: window popping open every time I start a REPL?

I love rainbow coloring of parens, but in Dark mode, the blue parens are almost impossible to see — is there a way to take out blue from the rainbow palette? Many thanks!!!

@genekim Yep, you can customise all the colours in Settings->Editor->Color Scheme->Clojure

@kenny I’m going to fix that shortly. Which REPL type are you using?

does cursive have any mitigation for the problem of jumping to the definition of a var that's defined by an unusual macro where the macro call doesn't actually mention the symbol?

(or is that supposed to work already?)

Any way to know the current priority of https://github.com/cursive-ide/cursive/issues/2010 ? Is there a different workaround than putting my resources directory in my src directory?

@joe.lane We currently store some configuration and that bug would break our whole workflow since most projects require that configuration. The configuration is stored in a project called config. If I start a REPL and try and slurp the config, as that issue shows, I also receive the IllegalArgumentException. However if I depend on the config project in my app project, I am able to slurp the config resource. Any resource within my app project still receives the IllegalArgumentException though.

Running (System/getProperty "java.class.path") shows that the resources directory is not on the classpath.

Looks like any path in :paths besides src is not included in the REPL classpath.

Same applies for :extra-paths in an alias.

What do you mean “project called config” ? an intellij project or a cursive project?

It's a Cursive Deps project.

Using the latest IntelliJ Community and Cursive plugin, I am getting the "symbol cannot be resolved" error. I have tried invalidating caches and restarting to no effect. In a require call I have [uncomplicate.neanderthal.vect-math :as vm :refer [exp! fmax fmax! linear-frac!] exp! cannot be resolved, but my own function that calls exp! compiles fine. linear-frac! (for example) can be resolved. Does anyone have a suggestion to solve this problem? [EDIT: ok, looking at the source code for the vect-math package, most of the entry points are defined using defmath or defmath! macros, and only the symbols of functions defined by defn are able to be resolved by Cursive/IntelliJ.]

@cfleming That changed worked great. Thanks!

Using amazonica, I get code completion in the repl. But in the editor, everything is cannot be resolved. I know amazonica is using Java reflection. Is that related? How come it’s working in the repl, though?

is there an easy / clean way to edit my ~/.clojure/deps.edn with Cursive? it wants to create a project around it... 😕

nevermind about the macro question, I found https://github.com/cursive-ide/cursive/issues/147

does anyone use liberator with cursive? Any way to get defresource to be recognized as a valid macro?

@alexkeyes hitting alt-enter and marking its resolution doesn’t work?

nope, because liberator uses the defresource macro in order to create endpoint resources for an API

for whatever reason it doesn’t resolve

@gfredericks No, unfortunately. Is this an internal macro or one I can look at?

Sorry, reading from the top, didn’t see the later comment to ignore.

@joe.lane Deps stuff is currently being worked on actively, I’ll hopefully look at that one today.

@chgraham You may be able to make that work by resolving those macros as either def or defn, depending on what they look like. See here for some (slightly out of date) details: https://cursive-ide.com/userguide/macros.html

@potetm Awesome! Thanks for letting me know.

@grav Resolution in the REPL works differently to the editor, it actually introspects the running environment. But if you’re using Amazonica, you should be prompted to create stubs which will make the resolution work in the editor too.

@onetom Not really, but I’ll add it to the to-do list since that would be useful.

@alexkeyes You should hopefully be able to make that work using: https://cursive-ide.com/userguide/macros.html, depending on what that macro looks like.