This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-15
Channels
- # announcements (1)
- # aws (79)
- # babashka (47)
- # beginners (82)
- # calva (65)
- # cider (27)
- # cljdoc (18)
- # cljs-dev (29)
- # clojure (189)
- # clojure-dev (5)
- # clojure-europe (3)
- # clojure-italy (1)
- # clojure-madison (6)
- # clojure-nl (4)
- # clojure-spec (10)
- # clojure-uk (41)
- # clojured (3)
- # clojurescript (5)
- # clojurex (17)
- # cursive (30)
- # data-science (7)
- # datomic (17)
- # emacs (3)
- # events (6)
- # fulcro (2)
- # funcool (9)
- # graalvm (29)
- # jobs-discuss (3)
- # joker (3)
- # kaocha (6)
- # malli (5)
- # music (6)
- # off-topic (21)
- # reagent (3)
- # reitit (4)
- # rewrite-clj (8)
- # shadow-cljs (49)
- # spacemacs (7)
- # sql (23)
- # tools-deps (15)
- # vim (43)
- # xtdb (19)
When I try opening one of my tools.deps projects, the window flashes on the screen and immediately closes. Stacktrace attached.
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.
No, you’re not, but this isn’t easy yet. It’s the next major thing I’m planning to add to Cursive.
Running a local nREPL with leiningen. Set up :dev :repl-options
including piggieback
middleware and CLJS repl launched from :init-ns
.
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?
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.
I’m planning to extend REPL commands to allow this, so that users can create commands with the behaviour they want.
Otherwise there’s a combinatorial explosion of <ways to select form>/<what to do with the result>
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? 🙂
Namespace name does not correspond to file system hierarchy...
What that means is that src/main/clojure isn’t a source root. Does the folder look blue in the project view?
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.
the src/main/clojure is not blue. but what comes next is. src/main/clojure/myproject
I solved it by going into Intellij and selecting the folder. Pressed: "Mark directory as: " 🙂
@UBN9SNVB4 The problem is that that will get reverted the next time you sync your pom.
I changed the structure of my project to be /src/clojure/myproject/core.clj
instead and the problem went away 🙂