This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-08-08
Channels
- # announcements (43)
- # architecture (4)
- # beginners (115)
- # calva (6)
- # cider (4)
- # circleci (4)
- # clara (3)
- # clj-kondo (6)
- # cljs-dev (10)
- # cljsrn (1)
- # clojars (1)
- # clojure (108)
- # clojure-boston (1)
- # clojure-dev (4)
- # clojure-europe (5)
- # clojure-italy (6)
- # clojure-nl (13)
- # clojure-uk (17)
- # clojurescript (47)
- # core-async (2)
- # cursive (13)
- # data-science (1)
- # datavis (15)
- # datomic (12)
- # graphql (5)
- # juxt (10)
- # kaocha (20)
- # lumo (1)
- # off-topic (27)
- # pedestal (4)
- # reitit (2)
- # shadow-cljs (115)
- # spacemacs (4)
- # sql (74)
- # tools-deps (79)
- # vim (15)
- # xtdb (2)
@cfleming I love the REPL-commands. One additional thing I would like to be able to do, is replace the selection with the result. Would that be possible?
This is a really cool one, I used to do this a lot in Emacs. You can then write parts of your program with Clojure
Yes, there are a lot of this sort of command that you might want to have, and I don’t want to implement them all and have a combinatorial explosion of possibilities. So my plan is to extend the REPL commands to allow you to build the ones you use yourself.
Is there a way to do this in Cursive? (Ctrl-Space - extend selection from Emacs). Similar to Ctrl-W in Cursive, but going forward, not up.
Yes, this is the best option right now. I’d like to implement “Extend selection left/right” too.
does anyone have a decent clojurescript+node.js+deps.edn+(n)repl workflow down?
@U3BALC2HH I usually use 2 REPL The first one, a regular cursive clojure REPL where I call:
(shadow.server/start!)
(shadow.api/watch :my-node-app)
Where the shadow-cljs.edn
looks something like this
{:deps true
:nrepl {:port 9000}
:builds {...
Then I start other "remote repl", connected on port 9000
This REPL is managed by shadow-cljs and I can call
(shadow.api/repl :my-node-app)
to "dig in" nodejs REPLok. I'm seeing online that you need to maintain a seperate project.clj
to "trick" cursive into playing appropriately with shadow-cljs ... is that still the case?
That's the main reason I've avoided shadow-cljs up until now
(also thanks for taking the time to respond!)
shadow-cljs can use "built in deps", deps.edn
or project.clj
#cursive just handle deps used at deps.edn
or project.clj
In that example, I'm using deps.edn
, but should work with project.clj too
okay I'll give that a shot