This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-25
Channels
- # arachne (1)
- # beginners (22)
- # boot (21)
- # cider (23)
- # cljs-dev (16)
- # cljsrn (9)
- # clojure (118)
- # clojure-dev (11)
- # clojure-greece (16)
- # clojure-italy (10)
- # clojure-losangeles (4)
- # clojure-russia (14)
- # clojure-serbia (4)
- # clojure-spec (58)
- # clojure-uk (33)
- # clojurescript (30)
- # cursive (17)
- # datomic (48)
- # docs (22)
- # events (1)
- # fulcro (24)
- # hoplon (3)
- # jobs (6)
- # jobs-discuss (4)
- # keechma (4)
- # leiningen (11)
- # luminus (4)
- # midje (1)
- # off-topic (107)
- # onyx (30)
- # other-languages (12)
- # pedestal (4)
- # re-frame (72)
- # reagent (6)
- # remote-jobs (1)
- # shadow-cljs (16)
- # spacemacs (3)
- # specter (9)
- # uncomplicate (4)
- # unrepl (40)
also check out unrepl (if you are interested) it does some amazing things in this department afaik
I think they are still based on the number of items in a collection. Anything else would be pretty controversial and technically speaking there’s 0 preventing us from doing this with nREPL - it just never came up/there was never time to work on this.
@mfm Nothing like this currently exists, but it’s definitely doable. Just a matter of time, which I don’t have much of. If someone’s interested in working on it - I can provide tips and help. Ideally this should handled in the middleware level - hooking into eval
and modifying its behaviour, but it can also be handled in Emacs directly - by just counting the size of the response chunks and truncating them after some point.
Not on github to "claim" this, but I'll take on the nrepl part of cider jack in for clojure tools
https://github.com/clojure-emacs/cider/issues/2180 <-- gift to you, @bozhidar
How does one tell cider to print the stacktrace into the repl buffer instead of opening *cider-error*
?
(defun cider-default-err-handler ()
"This function determines how the error buffer is shown.
It delegates the actual error content to the eval or op handler."
(if (cider-nrepl-op-supported-p "stacktrace")
(cider-default-err-op-handler)
(cider-default-err-eval-handler)))
ok, maybe there's a trick that q
quits the buffer. Haven't used cider for a while, generally dislike haveing many buffers opened.
the default err-eval-handler will just print the stacktrace. if you wanted to create a defcustom so that logic was stacktrace op is supported and desired then ...
@bozhidar I’m not getting notifications for issues filed against helm-cider
: https://github.com/clojure-emacs/helm-cider/issues
Maybe b/c I’m not a member of that organization? Can you fix that?
@U2J7JRTDX do you watch the repository?
Helm cider is awesome - thanks for working on it