Fork me on GitHub
#cursive
<
2019-11-15
>
flowthing07:11:51

When I try opening one of my tools.deps projects, the window flashes on the screen and immediately closes. Stacktrace attached.

flowthing07:11:09

Deleting .idea/workspace.xml is one workaround.

flowthing07:11:47

IDEA 2019.3 BETA

cfleming08:11:08

Hmm, I’ll take a look at that and see if I can figure it out.

flowthing08:11:42

Thanks! Let me know if you need any additional info.

deas07:11:01

Hope, I'm not asking for too much, but I'd like to launch ClojureScript + Clojure repls at once so I can throw forms at them from .clj and .cljs buffers.

cfleming07:11:24

No, you’re not, but this isn’t easy yet. It’s the next major thing I’m planning to add to Cursive.

👍 12
sooheon16:11:01

This along with auto-sending to the right kind of repl would be awesome 🙂

cfleming20:11:20

Yes, I’m definitely planning that.

deas07:11:44

Running a local nREPL with leiningen. Set up :dev :repl-options including piggieback middleware and CLJS repl launched from :init-ns.

deas08:11:40

This works but I have to wait for the Clojure repl connection to establish before I can start the figwheel repl using start. Once both repls are up. I need to change the dropdown clj/cljs to be able to send from corresponding buffers. Is this normal and expected today?

deas08:11:33

Got one more issue. 😜

deas08:11:53

Fixed it myself. Sorry for the noise. 😂

sooheon16:11:39

Is there an issue for addition “Send to repl…” command feature requests? I quite enjoy eval result to comment that lispy offers (see image). Multiple evaluations would overwrite comment. Calva has a display on the right side, cider also has a mode where results show and live update. These would be more difficult, but I think comments to file is a great simple solution.

cfleming20:11:06

I’m planning to extend REPL commands to allow this, so that users can create commands with the behaviour they want.

❤️ 8
cfleming20:11:42

Otherwise there’s a combinatorial explosion of <ways to select form>/<what to do with the result>

cfleming20:11:00

I’m also planning the overlay view like Calva, I have a PoC in a branch.

👍 4
sooheon09:11:54

Awesome, looking forward to it.

dangercoder20:11:22

I have a maven project with the structure: src/main/clojure/example/core.clj the core.clj namespace is called example.core in my core.clj file and cursive warns about it. Is there any way to remove* the warning? 🙂

cfleming20:11:34

What’s the warning you’re receiving?

dangercoder21:11:26

Namespace name does not correspond to file system hierarchy...

cfleming21:11:30

What that means is that src/main/clojure isn’t a source root. Does the folder look blue in the project view?

cfleming21:11:10

I seem to recall that the Maven Clojure plugin had a problem with this, and the IntelliJ Maven integration didn’t create source roots for whatever reason.

cfleming21:11:31

You might have to manually add an extra source folder in your pom.

dangercoder21:11:21

the src/main/clojure is not blue. but what comes next is. src/main/clojure/myproject

dangercoder22:11:09

I solved it by going into Intellij and selecting the folder. Pressed: "Mark directory as: " 🙂

cfleming07:11:56

@UBN9SNVB4 The problem is that that will get reverted the next time you sync your pom.

dangercoder15:11:29

I changed the structure of my project to be /src/clojure/myproject/core.clj instead and the problem went away 🙂