This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-29
Channels
- # aleph (2)
- # architecture (1)
- # beginners (5)
- # boot (7)
- # cider (24)
- # clara (28)
- # cljs-dev (7)
- # cljsjs (3)
- # cljsrn (24)
- # clojure (145)
- # clojure-italy (2)
- # clojure-nl (7)
- # clojure-uk (54)
- # clojurescript (159)
- # cursive (49)
- # data-science (8)
- # datomic (23)
- # editors (10)
- # emacs (2)
- # fulcro (123)
- # graphql (12)
- # hoplon (2)
- # java (23)
- # jobs (1)
- # jobs-discuss (2)
- # leiningen (17)
- # mount (5)
- # nrepl (5)
- # off-topic (20)
- # om (2)
- # onyx (25)
- # parinfer (2)
- # pedestal (1)
- # re-frame (8)
- # reagent (7)
- # ring-swagger (1)
- # shadow-cljs (24)
- # spacemacs (7)
- # specter (6)
- # tools-deps (7)
- # vim (2)
Sorry that I wasn’t around then - I’ve been doing Elisp for so long that I just automatically enable lexical binding everything. Files without it seem unnatural to me.
just an FYI: upgrading clojure-mode
and cider
from MELPA a fews minutes ago resulted in: https://github.com/clojure-emacs/cider/issues/2361
Hi. I’m trying to jack-in
clojurescript repl. it seems like it’s all working fine - it says connected
at the bottom of the screen but when I try to evaluate anything, it says that I need to jack-in clojurescript repl
@bravilogy yes you need C-c M-J
for the clojurescript REPL...depending on your cider-default-cljs-repl
it will create the desired one
another error I’ve encountered today a few times was
nrepl-send-sync-request: Sync nREPL request timed out (op eval code
@bravilogy probably more context is needed, which cljs REPL are you using (figwheel, shadow...). Personally I am using figwheel-main
and/or shadow
and I don't see that error
(I am on latest master though)
yeah it can be, it seems there are many moving parts there I would start asking in #spacemacs
Try it without +cider. I remember looking at this recently and it's not necessary. (I think)
I just updated things, now I can't jack-in it says: Lisp nesting exceeds ‘max-lisp-eval-depth’
is this known issue, any quick workarounds?
Sorry for all the problems this caused. Was juggling 20 things and edited the wrong thing…