This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-01
Channels
- # 100-days-of-code (2)
- # announcements (3)
- # beginners (95)
- # bitcoin (1)
- # cider (18)
- # cljdoc (9)
- # cljs-dev (8)
- # clojure (55)
- # clojure-austin (1)
- # clojure-berlin (4)
- # clojure-italy (21)
- # clojure-nl (1)
- # clojure-russia (2)
- # clojure-spec (47)
- # clojure-uk (31)
- # clojurescript (19)
- # component (8)
- # cursive (5)
- # data-science (2)
- # datomic (33)
- # emacs (7)
- # events (1)
- # figwheel (8)
- # fulcro (16)
- # graphql (27)
- # hyperfiddle (5)
- # jobs (1)
- # jobs-discuss (85)
- # keechma (7)
- # luminus (11)
- # mount (6)
- # off-topic (23)
- # onyx (1)
- # re-frame (4)
- # shadow-cljs (29)
- # specter (19)
- # tools-deps (11)
- # uncomplicate (3)
Hello guys!! a quick question: is there some kind of a "backward" command in CIDER INSPECT?? MANY THANKS!!!
If you mean 'go back up one level' when you've 'drilled into' a specific data structure? I think l
does that (that's the letter L
but lowercase)
could you tell me the name of that command please? I use spacemacs with vim keybindnings for navigating, so " l " means just move one char right in my case((
For posterity: it's cider-inspector-pop
Does anyone else not see "clojure-toplevel-inside-comment-form" available in clojure mode?
I'm using spacemacs, so maybe it's another spacemacs issue, but I can't seem to find this function.
clojure-mode 20180925.330 and CIDER 0.18.1snapshot and nREPL 0.4.5 and emacs 25 are installed
I’m running into an issue with Cider 0.18.0 where I execute cider-eval-region
or cider-eval-last-sexp
but instead of just executing that code, it appears (from output of *Messages*
) that the entire namespace is being evaled each time, which times out and gives an error. From my search on cider issues, it seems like there was a change to how REPL connections work recently - is there a way to debug what’s happening in this connection? Or maybe I need to change my workflow somehow?