ah, I didn't think about this at all

likely we just forgot about the stderr

although in this code example it seems to me that the stderr shouldn't be attached to the server process

@jan.zy: please, file this as an issue and we'll investigate it further

in cider-nrepl?

@samedhi: Did you file that issue after all? I can't seem to find it now

@samedhi: Never mind, I'm just being stupid. 😛

In 0.10.2, I'm often getting Wrong number of arguments: (0 . 0), 1 errors when trying cider commands. I don't get them when calling (load "dash") right before calling the cider command, but am not sure whether it is directly related (got that from https://github.com/clojure-emacs/cider/issues/1343). is there anything I can do to fix it?

stop using clj-refactor.el

cider doesn’t use dash.el anymore, so if you run into a problem like this - it’s definitely outside cider

thanks! i'm not using clj-refactor.el directly but will try to find out what includes dash.el then

ok apparently dash was just installed (maybe as a dependency of some old package), removed it

not so optional in my setup after all: https://gist.github.com/sander/5ce380b9be68a3e68dbb

reinstalled with only the packages i really need, things work now!

well, start using clj-refactor.el @sander 😉 and 😜 for @bozhidar

it is a nice package apart from the small beauty spot that it uses dash 😜

actually, just watch a 5mins episode of http://parens-of-the-dead.com

haha checked your gist, it seems clj-refactor is in a good company with magit 😉 — pun aside I understand the reasoning behind as few deps as possible @bozhidar 😉

sure, I was just joking myself

as usually the dash.el issues are coming from clj-refactor

and before this they were coming from cider itself

yup i know you were joking, no worries

tbh the main value dash still has that it brings elisp dev much closer to clojure coding

@bozhidar: Hi Bozhidar, you can persist the command history to a file?

@fenton: which history? the repl history?

@arrdem

yes

@fenton: in the repl buffer just C-x C-s and it'll prompt for a location to save the repl history to.

there's also options documented in the CIDER README for saving history on every REPL command as well as for what file to save it too.

https://github.com/clojure-emacs/cider#repl-history

@arrdem okay...sorry i missed that...that is exactly what I'd be looking for!

@fenton: quite alright happy hacking!

@arrdem: thank you guys for suck an awesome product!!!

*such!

lol

oops

I can take no credit for cider 😛 I'm just a user.

@arrdem: well thanks for helping me anyway!

I do have a series of fine libraries and http://conj.io which may be useful to you

/s

ah this file only gets written on a clean exit...what wondering about continuous writing to it for recovery from a laptop crash

I have a snippet for that...

ooooh

pray tell !

(require 'advice)
(advice-add 'cider-repl--add-to-input-history
            :after #'(lambda (x)
                       (cider-repl-history-just-save)))

also

(define-key cider-repl-mode-map (kbd "C-x C-s")
  'cider-repl-history-save)

@arrdem: hmmm...doesn't allow me to enter things in my repl anymore... Is this intended to persist after each command in the REPL? Or requiring an explicit save of it?

@fenton: advice is a way to chain functions together... that first snippet should just cause history to be saved after every sent command.

if the history file is set.

@arrdem: ok got it, hist file has to be explicitly set.