This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-16
Channels
- # arachne (1)
- # beginners (27)
- # boot (17)
- # cider (10)
- # cljs-dev (5)
- # cljsrn (76)
- # clojure (59)
- # clojure-austin (2)
- # clojure-brasil (1)
- # clojure-greece (76)
- # clojure-mexico (1)
- # clojure-quebec (63)
- # clojure-russia (16)
- # clojure-spec (127)
- # clojure-uk (12)
- # clojurescript (72)
- # community-development (7)
- # core-async (3)
- # core-matrix (2)
- # cursive (13)
- # datomic (8)
- # emacs (4)
- # funcool (4)
- # hoplon (148)
- # immutant (5)
- # keechma (2)
- # lambdaisland (5)
- # lein-figwheel (15)
- # leiningen (20)
- # off-topic (23)
- # om (13)
- # om-next (19)
- # onyx (11)
- # planck (11)
- # re-frame (59)
- # reagent (14)
- # rum (34)
- # specter (30)
- # spirituality-ethics (16)
- # uncomplicate (5)
- # untangled (387)
- # yada (2)
@bozhidar: I am looking to continue to improve org-babel-clojure. The next thing I am looking to do is to detect possible exception raised in the code that is being executed. However due to my lack of nrepl knowledge, I am not sure it is possible. Right now if you run code in a Org-mode code block and if there is an exception, then it is just silent. You have to switch to the major mode to get the exception screen. If there some API in nrepl that would tell me if an exception got throw, and if so to get that exception (such that I can display it)? Right now, depending on the mode I am using, org-bable-clojure uses nrepl-sync-request:eval or nrepl-request:eval to communicate with nrepl
@bozhidar: ok forget this, I found my way with "ex", "root-ex" and "err" from the nrepl response
@bozhidar: ahahah right 🙂 Will write a post about my latest upgrades, and will try to take the time to propose it to Org-mode and then to let Nicolas committing it to the master
Thanks. 👍 on manual. I had looked under https://cider.readthedocs.io/en/latest/configuration/ hoping to find something