@vincent.cantin There is a plan to investigate it, yes. There are some interesting implications, because REBL has the GUI in the actual REPL process, whereas with Cursive the GUI is in an external process (IntelliJ itself). I still don’t know what the full implications of that are, so no promises.

@kenny I’m testing the git lib missing SHA fix. However I can’t reproduce what you’re seeing - for me, if the SHA is invalid, then when I refresh the project the Build toolwindow pops up with a pretty clear message. Is there some other circumstance when that’s less visible?

Hi, I'm trying to create a deps.edn project and got the error 'Cannot execute: Clojure command not configured'. I installed Clojure using brew on mac and the clojure command is in my PATH. Is there another PATH I have to set up in IntelliJ?

Hi there

Hi - I sent something to the mailing list, but I wonder if this would be a better place for it: is it possible the Organize Imports function will ever work. I would love Cursive to clean up my :requires and :imports

Hi, I wonder if anybody had any trouble with Cursive v1.8.1-eap2-2018.3, tools.deps and Clojure 1.10.0.?

perhaps you could explain what trouble you’re seeing?

Sure. Let’me grab the details here

clj -A:main

I do have clojure 1.10 installed via brew

does your deps.edn :paths match the root of your source?

This is my deps.edn

:main
  {:extra-paths ["src"]
   :main-opts ["-m red-robin.main"]}

Same structure on Cursive

Cursive debug config

I wonder if this is related to have clojure 1.9.0 in tools.deps, but also having clojure 1.10 installed by brew :thinking_face: I even tried to downgrade clojure to 1.9.0 but could not using brew.

that shouldn’t matter at all

any brew installation should work with any Clojure version

Using brew, I can only install 1.10. Could not figure out how to install 1.9 after 1.10 was released.

My project currently does not run on 1.10

Call to clojure.core/ns did not conform to spec.

After upgrading to 1.10, Cursive stopped working, that is why I suspected a relation. But I think Cursive also upgraded, so now I am not sure what was the cause.

you can use something like brew switch clojure 1.9.0.397 to switch to a different (older or newer) version

I have tried that, but got

Error: clojure does not have a version "1.9.0.397" in the Cellar.

The only 1.9.0 that I have was installed by Cursive through maven

well, it has to be a version you’ve installed in the past - brew info clojure

I don’t think Cursive does anything with brew. you may be confusing two different things here

Maven is used to download versions of the clojure jar (the language itself) - those versions are usually like 1.9.0 or 1.10.0

I know. What I am saying is that on brew I can only get clojure 1.10

$ brew info clojure
clojure: stable 1.10.0.411
The Clojure Programming Language

/usr/local/Cellar/clojure/1.10.0.411 (9 files, 21.1MB) *
  Built from source on 2019-02-11 at 10:58:02
From: 
==> Dependencies
Required: rlwrap ✔
==> Requirements
Required: java >= 1.8 ✔
==> Analytics
install: 2,988 (30 days), 12,022 (90 days), 41,661 (365 days)
install_on_request: 2,949 (30 days), 11,821 (90 days), 40,716 (365 days)
build_error: 0 (30 days)

brew is used to install a version of the clojure and clj tools which have versions like 1.9.0.397 or 1.10.0.411

But in my deps.edn I have org.clojure/clojure {:mvn/version “1.9.0”}

the tools are the things that let you run clojure or clj at the terminal

Got it. I saw the source for the bash scripts.

many tools (clj, lein, boot, Cursive, etc) may cause the Clojure jar to get downloaded and cached in the Maven repository

that error you posted before (Call to clojure.core/ns did not conform to spec.) will prevent a namespace from loading, so is likely to be a problem for you

That only happens when I change deps.edn from 1.9.0 to 1.10

I will try to go deeper into what Cursive is trying to run, to check out why 1.9.0 is failing.

Thanks @alexmiller 🙇

Interesting. From the shell, both versions below do work

clj -m red-robin.main
clj -A:main

Clojure 1.9.0
nREPL server started on port 64956 on host 127.0.0.1
Exception in thread "main" java.io.FileNotFoundException: -m red-robin.main (No such file or directory)
	at java.io.FileInputStream.open0(Native Method)
       ...
	at clojure.main.main(main.java:37)

public static void main(String[] args) {
        REQUIRE.invoke(CLOJURE_MAIN);
        MAIN.applyTo(RT.seq(args));
    }

Found a clue. The difference between Intellij and tools.deps from cmd line is:

-javaagent:/Applications/IntelliJ IDEA  IDEA 

That only means that Cursive is assembling the classpath just right, and invoking

clojure.main -m red-robin.main