Option to opt-out of automatically starting metals

[lrytz]

Is your feature request related to a problem? Please describe.

When I open a single Scala file outside a project, VS Code starts metals.

I often edit random test files (without any scala-cli pragmas) and see a lot of semantic errors because metals doesn't have the right context.

Describe the solution you'd like

I would like to have an option to disable automatically running metals on single files.

Even with that option enabled, it would be useful to have a trigger to actually run metals after opening a file.

Describe alternatives you've considered

🤷‍♂️

Additional context

No response

Search terms

single file scala-cli

[lrytz]

Actually, I would like that option not only for single files, but for metals in general.

When opening any directory in VS Code and then a Scala file within it, there are 4 synthetic subdirectories created that I later have to clean up (.bsp, .metals, .scala-build and .vscode).

For example, when I open a single test folder fom scala/scala (like https://github.com/scala/scala/tree/2.13.x/test/files/pos/t2409) and then open the t2409.scala file, these four . folders are created.

[tgodzik]

You could disable the metals plugin and enable it per workspace. I don't think we need another mechanism for that.

[lrytz]

Ah, thanks that helps.

I see another option is to set up a profile in vs code.