Chris Kipp

I just looked into this as I thought it'd be an easy fix, and that we could mimic the way that it's done in scala-cli, but it's made much harder...

I actually don't get why this is happening since this looks correct when you look at the `generatedSources`: ``` ❯ mill showNamed scalatags.jvm\[3.1.3\].test.generatedSources [1/1] showNamed { "scalatags.jvm[3.1.3].test.generatedSources": [ "ref:7d898225:/Users/ckipp/Documents/scala-workspace/com-lihaoyi/scalatags/out/scalatags/jvm/3.1.3/test/generatedBuildInfo.dest" ]...

Ah shoot, I was still on Bloop instead of `mill-bsp`. Ugh, sorry. So this is actually an issue then probably with the Bloop export. Actually looking further I don't even...

Alright... digging even further. I think the only way we can do this with Bloop would be to utilize `sourceGenerators`. However looking at https://github.com/scalacenter/bloop/pull/1774 it's not super clear to me...

Ah annoying, so I tried to bump to 22.3.0 since I was having issues locally with that, but then I also see that the way it's installed in CI now...

I haven't forgotten about this @guizmaii, just been swamped with other stuff. I will get back to it soon.

Actually it seems like this is fixed in https://github.com/neovim/neovim/pull/24903, but needs to wait until the next release.

Sorry I missed this @pritchett. I'm unable to reproduce this however. I am using the following to test: ```scala //> using scala 3.4.0 //> using dep "org.scalatest::scalatest:3.2.18" class ExampleTest extends...

Good question @kluen. There's noting that nvim-metals really needs to do _apart_ from setting a default. Right now the default is something called `show-message`. So if they user doesn't set...

> If I understand correctly, the new change in metals does not allow both status bar and LSP progress at the same time, so we have three mutual exclusive options...