Metals improvements feedback

Tooling
21

Actually it is not so when I am opening new project.

When I open new project metals add metals.sbt file which enables semantic.db. So a click on file on any project starts compilation which is quite long, It seems longer than sbt compilation at least because there are no parallel compilation.

So to start work comfortably with a big multi project I should:

  1. Add metals.sbt file manually
  2. Run compile and Test / Compile
  3. Open vscode

It is not obvious for beginners at all .

May be vscode should compile all projects after first start.

IMHO: It is much more comfortable to wait full compilation to start work comfortably than to wait irritable long compilation on each subprojects at navigation.

22

Well, here’s a suggestion: show the output of sbt during project import. Because that takes forever and it’s really frustrating when you don’t even know what it’s doing.

23

Also: correctly supervise the bsp subprocess. When the bsp server crashes, metals should notice that, and not tell me it’s been compiling for 3 hours or something.

2 Likes
24

And metals should correctly close the server after exit vscode.

Now I must kill java processes manually to start sbt console.
Otherwise I am getting an error:

[error] server failed to start on local:sbt-server-e891cff5549b62420618. java.io.IOException: Could not create lock for \\.\pipe\sbt-server-e891cff5549b62420618_lock, error 5
sbt:PgTest>