Thanks for the kind words! It looks like goose is a deps project, so you probably want: https://cursive-ide.com/userguide/deps.html#working-with-aliases

@cfleming I added all aliases in the Clojure Deps toolwindow, added load.clj as source root & restarted IntelliJ. Still I'm facing same issue.

I cannot even load the file into REPL despite it being configured in REPL's config

It works after I've done Add source root in IntelliJ

@U03HVBGMRJ5 When you select the aliases in the toolwindow, you don’t have to restart IntelliJ, just refresh the project from the toolwindow. So, could you open the toolwindow and refresh the project now?

Once you’ve done that, does the perf folder appear as a source root? It should be the same colour in the project view as the src folder.

> just refresh the project from the toolwindow Doing this doesn't fix the issue > Does the perf folder appear as a source root? It should be the same colour in the project view as the src folder This happens only after I click on Add Source root from IntelliJ, not by adding the alias from Deps toolwindow

@cfleming all these changes disappear upon restart 😓

One thing I’ve just noticed, shouldn’t the key in the :perf alias be :extra-paths instead of :paths in Goose’s deps.edn?

@cfleming modifying Clojure Deps tool window & s/:paths/:extra-paths/ fixed the issue. cc @U38004EG7 I had modified :perf alias in the past to see if :paths worked. Thanks a lot :hugging_face:

So, there isn’t at the moment, but JetBrains have recently added the ability to do that in toolwindows and I’m planning to add it for REPLs. There are some open UX questions about how it should work. Currently, sending forms to the REPL send to the currently selected REPL, which is harder to determine if there are multiple REPLs visible at once.

Another option is to allow the user to open the REPL in a normal editor rather than a toolwindow, then you could just arrange them using the normal editor arrangement commands. It still has the same problem of identifying where to send forms etc.

Yes, sending automatically to the proper REPL would further accelerate development. Sending based on to what module the file belongs could be a nice first guess. Doesn't work for multiple REPLs running from the same module of course. In that case, the last one might be a good guess. I'm not sure if many people use to have several REPLs for the same module.

Well, having one for clj and another for cljs would be a common use case. When sending forms from clj or cljs the correct one could be chosen based on the file type, but cljc is trickier.

I’m very unlikely to support Midje. It has been effectively dead for ages and is a tangled mass of macros. Sorry 😞

@cfleming What is “Run ‘x-test’ in REPL” doing? I was curious if I could get a macro that evaluates to a deftest to be evaluated similarly.

I think you can run Midje tests by just using deftest directly and having Midje assertions in the tests.

Are you using tools.namespace? I sometimes see this when reloading namespaces. I have never investigated but it seems to be some kind of race condition and the error has not impacted my development.

I don’t get it when running JDK 8 or 14, but always when using 17, so that looks a bit less than a race condition then

we've been using Java 17 at work shortly after it was released and have never seen this error. is it possible for you to post the full stack trace?

I cannot, because it doesn’t happen on the same thread

if I say *e it just returns nil

I saw the error lately, but it happens very rarely

im on M1 macOS 13.0.1 (22A400) /nix/store/280df465g5isik8ljjnc8c31ncq2s4is-zulu17.34.19-ca-jdk-17.0.3/bin/java

Ok, good to know :)