Fork me on GitHub

Hi, I am having a similar issue to earlier - connecting to the same nrepl server twice using socket-level connections (not Emacs-Cider). I'm confused about how message routing works- messages sent back which are seen in the first socket don't seem to be seen in the second, and ls-sessions returns an empty list (!?) even though the first session has successfully called clone


reading further (I posted this on nrepl too), I think this is just how nrepl works, I didn't realize, and you'd need to use something like "concerto" to create what I thought would be the default behaviour


you had an expectation that if two sessions were connected, if you evaluated something in one session it would send the result messages to both sessions?