my emacs nrepl buffer prints all the bytes from all the messages coming in over websocket; can i turn that off?

@ajs Can you elaborate on this?

What do you call an nrepl buffer?

in emacs cider, there is a buffer for nrepl in addition to the buffer for the repl

i'm using jetty websocket client and all incoming bytes are printing in that nrepl buffer, which is a lot

I see. Well, I guess that’s the stdout that got bound to the output of the nREPL process. Not sure what we can do about this. What kind of problems does this create for you? Normally people don’t interact with that buffer at all.

well, logging in general can be rather time consuming. the problem is that a message comes in and normally it would be parsed and the app would proceed to handle another message. But all that logging is I presume responsible for why the parsing for each message is taking much much longer than it should. I've tried timing various things in my app and they are all a few ms which is no problem, yet something is causing messages to take seconds for parsing, and i know from experience that logging is a real time-consuming activity

when i watch the nrepl buffer, it's just a huge streaming log of bytes for a single message, and if I could disable that, it would be interesting to see if that impacts performance

I see. I doubt that logging is happening over the nREPL connection, otherwise the output wouldn’t end up there, but you can file some ticket with steps to reproduce this problem and we can take a look at the problem.

At the very least it’d be interesting to know what’s going on. Btw, generally it’s best to ask such questions in #cider.

i'll continue in #cider

is there a way to see what action occurs in emacs. Say some alignment is wrong and I want to know what exact function kicked in at that time unrelated to a key stroke?

@theeternalpulse you could try with the profiler running with