Fork me on GitHub
#cider
<
2019-12-11
>
bozhidar07:12:53

Quite insightful!

dromar5610:12:33

Any way of not sending the result of eval functions (like C-x C-e) to the echo area? I'd prefer to only have the result as an overlay

bozhidar21:12:40

@dromar56 Set cider-use-overlays to nil.

dpsutton21:12:37

that would inhibit the message?

bozhidar21:12:38

My bad. I misread the question. No, I think we didn’t make this part customizable.

bozhidar21:12:00

My bad. Actually we did. 😄

bozhidar21:12:23

If you set cider-use-overlays to t it doesn’t show results in the minibuffer.

dromar5601:12:56

Oh perfect! I knew about cider-use-overlays but not about that effect

dpsutton21:12:55

thoughtful @malabarba

bozhidar21:12:44

Indeed! Also a master of confusing defcustom names. 😄

rjray23:12:53

Has anyone seen cider-jack-in given an error of, "Direct connection to localhost:XXX failed"?

rjray23:12:30

This is a Linux (Ubuntu) machine, with CIDER et al all up to date. I have a similar machine at home (Ubuntu, same version) that starts the REPL just fine.

dpsutton23:12:34

Can you check the messages buffer for the command that CIDER runs and try running that command in the terminal

rjray23:12:38

Well, to muddy it up a bit more... if I exit/restart emacs, I can jack in. It seems to be a problem only after I kill a nREPL session and try to start a new one.

rjray23:12:44

Also, when it has failed to create a session, there is still a running java process in the background, running the nREPL code. If I kill that process, I get a notification message in emacs. Even though I had no active connection to a nREPL...

bozhidar14:12:49

What are the exact commands you’re using?

rjray20:12:55

I'm not sure. I just call cider-jack-in, and it starts the nREPL. This process starts up successfully, and is running (I can check this with ps). For some reason, emacs itself is not able to get the connection to the given port on localhost.