This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-16
Channels
- # announcements (7)
- # babashka (1)
- # beginners (125)
- # bristol-clojurians (4)
- # calva (49)
- # cider (10)
- # cljs-dev (3)
- # clojure (102)
- # clojure-berlin (3)
- # clojure-czech (4)
- # clojure-europe (84)
- # clojure-france (29)
- # clojure-italy (2)
- # clojure-nl (26)
- # clojure-norway (5)
- # clojure-spec (4)
- # clojure-sweden (4)
- # clojure-uk (50)
- # clojurescript (3)
- # community-development (2)
- # conjure (19)
- # cursive (9)
- # datascript (4)
- # datomic (33)
- # fulcro (4)
- # off-topic (26)
- # parinfer (10)
- # pedestal (4)
- # quil (8)
- # re-frame (1)
- # reagent (20)
- # remote-jobs (5)
- # reveal (53)
- # sci (10)
- # shadow-cljs (37)
- # spacemacs (6)
- # sql (25)
- # tools-deps (24)
- # vrac (2)
- # xtdb (10)
Is there a trick to bind *print-length*
only for cursive repl without making it affect other printing parts of the running program?
does cursive still have compatibility issues with deps? related to the shadow-cljs dependencies
What is the best form to choose when resolving a macro that looks like this? When using the defn1
and defn2
functions that are produced from here, these are unable to be resolved by Cursive. I’ve tried a few easy options, but I’m not familiar with a form in Clojure that I could tell Cursive to resolve this in a decent way
(defmacro two-defns
[defn1 defn2]
`(do
(defn ~defn1 ...)
(defn ~defn2 ...))
Is it still true that figwheel & cursive don't get along well in tools-deps projects? read it here: https://figwheel.org/docs/cursive.html
I don't use Cursive myself, but most of my coworkers do and we have not had issues porting our figwheel based projects to deps