This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-13
Channels
- # beginners (78)
- # boot (27)
- # cider (13)
- # cljs-dev (41)
- # cljsrn (4)
- # clojure (216)
- # clojure-android (1)
- # clojure-conj (6)
- # clojure-greece (1)
- # clojure-italy (11)
- # clojure-russia (127)
- # clojure-spec (63)
- # clojure-uk (34)
- # clojurescript (68)
- # core-async (5)
- # cursive (5)
- # data-science (1)
- # datomic (4)
- # dirac (11)
- # editors (7)
- # events (1)
- # graphql (12)
- # hoplon (39)
- # jobs (1)
- # liberator (3)
- # lumo (101)
- # off-topic (14)
- # om (3)
- # onyx (3)
- # parinfer (14)
- # re-frame (10)
- # reagent (2)
- # remote-jobs (1)
- # ring-swagger (17)
- # sql (21)
- # untangled (38)
- # vim (3)
- # yada (23)
i’m calling cider-interactive-eval in lisp , but it doesn’t popup exception with stack trace
@jasonjckn are you invoking cider-interactive-eval
via call-interactively
?
jasonjckn: if you want to share that keysetup/lambda, I could try to re-produce. I expect it needs to be wrapped with call-interactively.
(spacemacs/set-leader-keys-for-major-mode 'clojure-mode
"eg" (lambda ()
(interactive)
(save-buffer)
(cider-interactive-eval "(try
(if (resolve 'user/stop!) (@(resolve 'user/stop!)))
(require 'clojure.tools.namespace.repl)
(clojure.tools.namespace.repl/refresh :after 'user/start!))
")))
within cider.el itself, all uses of cider-interacive-eval are within a an emacs-lisp interactive function (one that has (interactive ..)
at the head of the fn - so yep, wrap with call-interactively should work.