Fork me on GitHub
#cider
<
2019-06-10
>
orestis10:06:34

Are you on the latest cider and supporting libs? nRepl, cider-middleware etc. I think I remember similar mysterious issues that went away after an update.

orestis10:06:51

If you are, I’d look into the various cider / sessman functions to try and see what cider thinks about your buffers. I always found the session management of cider to be a little confusing, probably because I don’t know much about emacs/sessman.

bozhidar11:06:53

Yeah, yeah. The documentation definitely needs some improvement. 🙂

bozhidar11:06:00

Very simply put on jack-in REPLs are mapped to the project that created them, so you can switch easily between REPLs for different projects and you won’t evaluate code from one project in the REPL for another project by accident.

bozhidar11:06:23

Everything on the subject (which is admittedly not much) lives here https://docs.cider.mx/cider/usage/managing_connections.html

bozhidar11:06:51

Generally the common problem people encounter is that they try to evaluate code in files that CIDER doesn’t consider part of the project owning the REPL. Turned out we didn’t initially consider all the setups people could possibly have. 🙂

camechis16:06:40

Might be a dumb question but I am new to using deps.edn but is there anything special that you need to do so CIDER sees deps that exist in a Test alias ? After jacking in it cannot find deps that exist in that alias for my test source.

dpsutton16:06:04

you need that alias. run the jack in with a prefix argument. (C-u C-c M-j) and it will let you edit the startup command. you can stick the alias on there