This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-12
Channels
- # announcements (2)
- # bangalore-clj (4)
- # beginners (97)
- # calva (57)
- # cider (24)
- # clj-kondo (1)
- # cljdoc (4)
- # cljs-dev (8)
- # cljsrn (6)
- # clojure (27)
- # clojure-berlin (7)
- # clojure-dev (95)
- # clojure-europe (16)
- # clojure-italy (15)
- # clojure-losangeles (9)
- # clojure-nl (8)
- # clojure-spec (10)
- # clojure-uk (29)
- # clojurescript (25)
- # clojutre (2)
- # clr (6)
- # cursive (33)
- # datomic (20)
- # dirac (1)
- # duct (9)
- # fulcro (2)
- # graalvm (18)
- # jobs (5)
- # jobs-discuss (19)
- # nrepl (4)
- # nyc (1)
- # off-topic (18)
- # pathom (15)
- # re-frame (22)
- # reagent (4)
- # reitit (1)
- # rewrite-clj (9)
- # spacemacs (2)
- # xtdb (12)
@bozhidar 1. I've connected to repsl via cider-jack-in-clj&cljs (I'm using shadow-cljs) 2. When I try to evaluate the form: #?(:cljs (println "Hello")) the expression is send to clj repl instead of cljs. The question is how can I send some expressions to clj repl and some expressions to cljs repl?
Guys, is there a way to debug functions defined with custom defn
s? I'm trying to debug a function declared through prismatic/schema
's defn
with no success
@bozhidar so there is no option to send value to cljs instead of regular clj repl?
At some point I recall we were sending forms to both REPLs when working with cljc, but I’m not quite certain what’s the current state. You can open some ticket and I’ll check this when I can.
@lvbarbosa Just an idea… If CIDER doesn’t support it… if that’s a macro that’s expanding to a defn
(I don’t know whether it is), you could use the macroexpansion in place of your definition.
Oh I thought it would show a text snippet. Well, that's the macroexpansion-1 of a function. I think I now understand why the debugger does not work on this
Maybe you could replace the things in that first let
with def
s, and then do the defn
at the top level (just for debugging purposes). And there’s also that thing after the defn
so you’d need that too.
Sir, apparently there is a way to do it.
When I try to instrument the function, it triggers the debugger. I was hitting C
to continue
at that moment. Subsequent calls to the instrumented function would not trigger the debugger
Instead of continue
, if you hit n
(`next`), the function is successfully instrumented. Subsequent calls do trigger the debugger
Ah, I think I recall that as a bug in an earlier version of CIDER. Are you on the latest version?
I'm using the latest version that is on MELPA: 20190911.1917
so weird
how can I configure emacs/clojure-mode/cider in such a way that it doesn't indent lines starting with a single semi-colon to the middle of the page?
I wonder if it's related to classic Emacs Lisp convention at all? https://ftp.gnu.org/old-gnu/Manuals/elisp-manual-20-2.5/html_node/elisp_656.html