There's this setting already:
Optional absolute path to an sbt executable to use for running sbt bloopInstall.
By default, Metals uses java -jar sbt-launch.jar with an embedded launcher while respecting .jvmopts and .sbtopts.
Update this setting if your sbt script requires more customizations like using environment variables.
But this is not honored.
It should at least be a flag one can set in the preferences that make Metals wait for a server instead of starting one.
But metals would sort of be unusable until that happened
So does starting sbt server first and then vs code work in this scenario?
Yes, it would, but I want to of course use the integrated terminal to avoid alt-tabbing between the windows. Most people prefer that I think.
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.