This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-11
Channels
- # adventofcode (31)
- # announcements (6)
- # babashka (5)
- # beginners (93)
- # calva (15)
- # cider (20)
- # cljs-dev (16)
- # clojure (159)
- # clojure-berlin (1)
- # clojure-dev (5)
- # clojure-europe (9)
- # clojure-italy (9)
- # clojure-losangeles (2)
- # clojure-nl (26)
- # clojure-spec (7)
- # clojure-uk (33)
- # clojurescript (54)
- # clojutre (5)
- # cursive (20)
- # datomic (23)
- # emacs (19)
- # events (1)
- # expound (1)
- # figwheel-main (1)
- # fulcro (104)
- # hyperfiddle (1)
- # jobs (1)
- # luminus (10)
- # malli (59)
- # nrepl (1)
- # off-topic (11)
- # pathom (5)
- # planck (15)
- # reagent (13)
- # reitit (8)
- # rewrite-clj (10)
- # ring-swagger (3)
- # shadow-cljs (129)
- # tools-deps (46)
- # xtdb (14)
- # yada (1)
@bozhidar interesting chart I made from the survey results: https://docs.google.com/spreadsheets/d/1qnuYelzWXrLhdCWHT1aqLZOggw9gC2DW8DWJPZCfSRY/edit#gid=772304059
Any way of not sending the result of eval functions (like C-x C-e
) to the echo area?
I'd prefer to only have the result as an overlay
thoughtful @malabarba
Has anyone seen cider-jack-in
given an error of, "Direct connection to localhost:XXX failed"?
This is a Linux (Ubuntu) machine, with CIDER et al all up to date. I have a similar machine at home (Ubuntu, same version) that starts the REPL just fine.
Can you check the messages buffer for the command that CIDER runs and try running that command in the terminal
Well, to muddy it up a bit more... if I exit/restart emacs, I can jack in. It seems to be a problem only after I kill a nREPL session and try to start a new one.