Adrien Piquerez

You need to install `scalafmt` command: https://scalameta.org/scalafmt/docs/installation.html#cli Then you should be able to run it: ``` > scalafmt ```

Thanks for the suggestions! I fully agree and support these changes.

> Looks like the reason for it is that first stop is not inside the for, but outside of it. @adpi2 any idea is that expected? Might be limitation. Yes...

Yes, if it is a Scala 2 entry it seems we had the `-Xsource:3` option. https://github.com/scalacenter/scala-debug-adapter/blob/50ba5c0cce6364ef2523c8ce5f340d2f86c0b547/modules/core/src/main/scala/ch/epfl/scala/debugadapter/internal/DebugTools.scala#L135 The reason for this is to be able to evaluate expressions in Scala 2...

> Though isn't the warning fatal by default with -Xsource:3 from what I see? Yes you're right. Then maybe adding `-Xmigration` will help.

> This was raised on discord and I can't remember what is the solution here, but the sbt console and BSP often conflict with each other. Can you give more...

@eed3si9n I would very much appreciate more details on this feature. I understand the goal is to offload some task execution from the graph engine but how? - How would...

RFC-4 intends to fix two issues: 1. BSP responsiveness issue 2. JIT vs stability As I explained in https://github.com/sbt/sbt/discussions/7653, I think those two issues should be addressed separately. And that...

I don't understand the goal here. If `Global / displayShell := false` and I do `sbt --client` does it start a client shell?

Bloop and sbt have the same problem. To run the tests, the current implementation in Bloop and sbt only accepts a list of test suites, as `List[String]`, in the `data`...