testwhen I want
Because SBTN is a buggy mess.
there has been a ton of work on the sbt side on sbtn, so please refrain from shitting on it here
It randomly disconnects, and selecting recent commands with [Arrow Up] or pressing tab for autocomplete bugs out if SBT is busy
Have these been reported to sbt?
you could possibly disable Metals for a workspace as well
Seems like you guys seem suggesting this, but it's way too cumbersome.
I asked a while ago why we couldn't stop Metals temporarily in case of broken builds and received the same answer, but the truth is going into plugin settings instead of issuing a command is just not ergonomic.
sbt bloopInstall, and that's what the "sbt script" setting is used for
bsp.trace.jsonfile as outlined here https://scalameta.org/metals/docs/contributors/getting-started.html#json-rpc-trace, that'd be the easiest way to see the communication
nvim --embedwith a UI embedding, and then somehow configuring that nvim instance to use metals. correct? would that be a reasonable approach? that way I could ditch a custom editor altogether, although the work will shift to implementing the nvim UI client. has anyone done such thing, implement the nvim UI API in a Scala app?