Fork me on GitHub
#shadow-cljs
<
2019-11-17
>
martinklepsch15:11:18

If anyone here is using Vim (Fireplace): did you run into issues with seeing println output from CLJS REPLs?

martinklepsch15:11:59

After switching into a CLJS REPL using shadow.cljs.devtools.api/node-repl I am not seeing any println output anymore.

martinklepsch09:11:35

Thanks. I’m connecting to a CLJ repl via cider and then run (shadow/node-repl) — if my reading of this issue is correct than println should at least work reliably on the first invocation of node-repl , but doesn’t for me. I will try reproducing with console shadow node-repl too

martinklepsch09:11:15

Note that this was working fine-ish with Emacs+Cider but is now not working with Vim+Fireplace.

martinklepsch09:11:41

Printing works on the first node-repl instance but doesn’t on subsequent invocations. (Just confirming what is written down in the issue already.)

thheller10:11:00

every editor seems to interpret the nrepl messages in a slightly different way. there doesn't seem to be a standard for that so I really don't know how everything is supposed to work. it all works fine in Cursive and that is what I test on. if you want to dig into why fireplace isn't happy I can change things (as long as that doesn't break any other editor).

martinklepsch11:11:16

Cool, I’ll try to figure out whats going on there. Thanks for the context, wasn’t sure on which side this should be considered an issue

thheller12:11:43

the problem likely is that the node-repl captures stdout/stderr and sends those without any nrepl message id

thheller12:11:57

fireplace likely either just drops them or displays them somewhere hidden

martinklepsch12:11:16

that indeed sounds very likely