Fork me on GitHub
#cider
<
2018-06-25
>
bozhidar05:06:44

You’re welcome!

manuel07:06:11

morning. Just an FYI: latest cider from MELPA works as expected now.

manuel07:06:32

and once again, thanks everybody for the prompt fixes πŸ™‚

bozhidar07:06:07

You’re welcome!

bja16:06:43

With the recent connection api work, is there a quick alternative to cider-current-repl-buffer?

dpsutton16:06:36

cider-switch-to-repl-buffer ? @bja

bja16:06:56

I think it's actually cider-current-repl

bja16:06:18

perusing the diff and testing it, this seems to be it

bja16:06:16

this broke my spacemacs since a ton of the custom spacemacs stuff runs through spacemacs//cider-eval-in-repl-no-focus which was using cider-current-repl-buffer

bja16:06:46

it looks like swapping (cider-current-repl-buffer) with (cider-current-repl) gets things back online

bozhidar16:06:50

@vspinu forgot to add obsoletion warnings in the initial PR. We’ll likely add them back before 0.18 is made final.

richiardiandrea16:06:37

@bja I was using cider-current-repl too

bja16:06:30

I'm prepping a PR for spacemacs. It seems I'm the lucky fool to both track develop and update his packages first

richiardiandrea16:06:58

thanks for doing that I would add πŸ˜‰ I am an Emacs Live user and I quit sending back patches because the repo and maintainer is not really responsive given the pace things evolve

richiardiandrea16:06:22

I maintain my own fork

andre.stylianos16:06:33

hey @bja I did that a few hours ago

bja16:06:02

so I'm the second person, sweet

andre.stylianos16:06:36

I had been a few days suffering from this, but today I actually had time in the morning to investigate and do the PR

bja16:06:52

I try to only update my spacemacs once every week or so

bja16:06:58

I like to track develop since I like bugfixes

bja16:06:13

but updating every day was too much time spent on stuff like this

andre.stylianos16:06:21

I update at random times, guess I was just lucky πŸ˜‚

bja16:06:44

@richiardiandrea I came to emacs (Spacemacs really) so I could stop maintaining my own vim distro

bja16:06:54

I was at the point I had a ~/.vim.d and realized I was recreating the emacs portion of cider atop a weird mix of tmux/vim-sexp/tslime/vim-fireplace

pablore18:06:55

So digging around my problem, it appears cider is doing npx server command instead of npx shadow-cljs server

pablore18:06:17

when doing cider-jack-in-clojurescript

pablore18:06:05

npx: installed 225 in 19.408s
command not found: server
which is the same result as doing npx server on the command line

dpsutton19:06:27

anyone know offhand how to link a buffer to a cljs repl? I'm a little confused why its not linked. Its the same project. same directory, it just doesn't "see" the repl

dpsutton19:06:44

kinda feels weird to run cider connect cljs to a repl that cider and emacs created

dpsutton19:06:30

oh. it's just based on last visited repl.

Timo Freiberg19:06:24

i'm currently looking at https://github.com/clojure-emacs/cider/issues/2317 (`(slurp in)` can't be interrupted) maybe someone can give me some early feedback πŸ™‚

Timo Freiberg20:06:20

i've been looking at cider-need-input in cider-client.el and it looks like the problem is that there's no way to send EOF via read-from-minibuffer. C-c C-c is not bound in minibuffers for me, I hope that's usual and not caused by spacemacs... therefore I close the minibuffer with C-g, which closes the minibuffer via signal. so i could change cider-need-input to catch the signal and send an EOF-equivalent to nrepl. nrepl seems to interpret an empty message as EOF according to this test: https://github.com/clojure/tools.nrepl/blob/master/src/test/clojure/clojure/tools/nrepl_test.clj#L403 any other suggestions? seems quite hacky