This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-05
Channels
- # beginners (240)
- # boot (5)
- # cider (48)
- # clara (2)
- # cljs-dev (3)
- # cljsrn (66)
- # clojure (111)
- # clojure-denver (2)
- # clojure-italy (42)
- # clojure-nl (5)
- # clojure-spec (12)
- # clojure-uk (45)
- # clojurescript (138)
- # community-development (7)
- # core-async (8)
- # datomic (27)
- # emacs (21)
- # euroclojure (6)
- # figwheel (10)
- # fulcro (29)
- # graphql (5)
- # hoplon (3)
- # luminus (1)
- # lumo (7)
- # mount (4)
- # off-topic (13)
- # onyx (20)
- # parinfer (3)
- # pedestal (4)
- # precept (1)
- # proton (3)
- # re-frame (41)
- # reagent (3)
- # reitit (28)
- # ring-swagger (7)
- # shadow-cljs (88)
- # specter (1)
- # testing (10)
- # tools-deps (27)
- # vim (58)
I was thinking of tackling a small task to add cwd info when boot starts up a repl. Is this something in boot or would I have to look toward tools.nrepl
mainly to trickle down to emacs to be able to load the .nrepl-port file properly when using cider-connect
could be a task, could also maybe add an -e
argument to the repl
task. like boot repl -e '(println "path=" (.getAbsolutePath (java.io.File. ".")))'
hm, nevermind, i guess that doesn't work with repl -s
I was also looking at doing something hacky like copying the n-repl file after it is created to a known directory, and checking that, but changing the cider code for something that specific isn't ideal