Fork me on GitHub
#cider
<
2016-06-23
>
escherize06:06:18

I'm not sure, but you may want to use forward-sexp instead of paredit-forward for those who use smart parens or just the built-in lisp.el.

helios14:06:56

hey guys, I'm encountering a weird error with cider (i'm not really sure when it started). Instead of showing the output of clojure.tools.logging/info to my *cider-repl* window, it's complaining about Error in process filter [nREPL]: no response handler with id nil found. nrepl.messages only shows the message that it was supposed to be logged, but no other messages. Cider seems to be hanging afterwards 😕

helios14:06:49

for now i switched away from tools.logging to a normal prn

helios14:06:40

or maybe the question is, how can i redirect the output of logging to cider-repl window?

dhruv115:06:19

question regarding cider debugger:

dhruv115:06:57

(defn add
  [& many]
  (apply + many))

(defn randomize
  [n]
  (rand-int n))

#dbg
(defn add-two-nums
  [n1 n2]
  (add (randomize n1)  (randomize n2)))
I want to debug add-two-nums. but every time there is a function call, i also want to know what’s going on in that function (in this case randomize and add.

dhruv115:06:11

is it possible to do that? if so, how?

malabarba17:06:17

@dhruv1: you can instrument those functions with #dbg too. Or you can step through the function with i instead of n.

dhruv117:06:04

ah! i i works perfectly.

dhruv117:06:44

the reason i don’t want to instrument those functions is because they can be in different namespaces.

benedek20:06:25

@robert-stuttaford: i am guessing the problem with project-clean is here: https://github.com/clojure-emacs/clj-refactor.el/blob/master/clj-refactor.el#L2649-L2650

benedek20:06:02

can you replace this with:

(when (and (not *cljr--noninteractive*)
             (buffer-modified-p))
    (save-buffer))
and let me know if it helped

josh.freckleton20:06:09

@escherize: ah, good advice, thx!