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?
--embed, it simply means it runs the full nvim but without its own UI, and then you use the RCP interface to receive UI events such as redraw commands, and the client is free to render that in whatever architecture (will be Java2D in my case).
bloop exitand restarted nvim/metals... not going away. Any suggestions?
I'm using metals+vscode+bloop on macOS/M1 where only the snapshot versions of bloop work. I've set "Bloop Version" settings to "1.4.8-45-8b51bdd9" and have the same version of bloop-jvm installed using coursier. Native "bloop" is not installed and the bloop is a symlink to bloop-jvm. I am absolutely sure there's not other bloop executable on my system.
Everything work fine and bloop version seems to be correct
ls -al `which bloop` lrwxr-xr-x 1 kamyar staff 64 Jun 4 13:28 /Users/kamyar/.local/bin/bloop -> /Users/kamyar/Library/Application Support/Coursier/bin/bloop-jvm ❯ bloop about bloop v1.4.8-45-8b51bdd9
Until once in a while things stop working and when I the check the running server version I get:
❯ bloop about bloop v1.4.8-19-4d9f966b
Where is this server version coming from and how can I stop this from happing?
Cleaning the project (+.bloop and .metals directories, metals.sbt files etc) and killing running java processes solves the issue for a while but it happens again in couple of days!
I also tried adding bloop-sbt plugin with the correct version to my project but it doesn't seem to be helping.