Anyone having autocomplete working in Scala 3 projects?

[jan0sch]

Hi,

I noticed that in my Scala 3 projects I don't have autocomplete via metals. With Scala 2 projects it works as usual and the Scala 3 ones do also have code navigation (jump to X) and so but no autocomplete. The default autocomplete of nvim/vim goes a long way, especially if a lot of files are in the buffers but for other stuff it is quite cumbersome.

Any ideas or something I am missing?

Kind regards,

Jens

P.S.:

config from init.lua:

local nvim_metals_group = vim.api.nvim_create_augroup("nvim-metals", { clear = true })
vim.api.nvim_create_autocmd("FileType", {
  pattern = { "scala", "sbt", "java" },
  callback = function()
    require("metals").initialize_or_attach({})
  end,
  group = nvim_metals_group,
})
metals_config = require("metals").bare_config()
metals_config.settings = {
  bloopSbtAlreadyInstalled = true,
  showImplicitArguments = true,
  showInferredType = true,
  excludedPackages = {
    "akka.actor.typed.javadsl",
    "com.github.swagger.akka.javadsl"
  }
}
metals_config.init_options.statusBarProvider = "on"

map("n", "<leader>ws", '<cmd>lua require"metals".hover_worksheet()<CR>')
map("n", "gf", "<cmd>lua vim.lsp.buf.definition()<CR>")
map("n", "gF", "<cmd>tab split | lua vim.lsp.buf.definition()<CR>")
map("n", "K", "<cmd>lua vim.lsp.buf.hover()<CR>")
map("n", "<leader>t", "<cmd>lua vim.lsp.buf.hover()<CR>")
map("n", "gi", "<cmd>lua vim.lsp.buf.implementation()<CR>")
map("n", "gr", "<cmd>lua vim.lsp.buf.references()<CR>")
map("n", "gds", "<cmd>lua vim.lsp.buf.document_symbol()<CR>")
map("n", "gws", "<cmd>lua vim.lsp.buf.workspace_symbol()<CR>")
map("n", "<leader>cl", [[<cmd>lua vim.lsp.codelens.run()<CR>]])
map("n", "<leader>sh", [[<cmd>lua vim.lsp.buf.signature_help()<CR>]])
map("n", "<leader>rn", "<cmd>lua vim.lsp.buf.rename()<CR>")
map("n", "<leader>f", "<cmd>lua vim.lsp.buf.formatting()<CR>")
map("n", "<leader>ca", "<cmd>lua vim.lsp.buf.code_action()<CR>")
map("n", "<leader>aa", [[<cmd>lua vim.diagnostic.setqflist()<CR>]]) -- all workspace diagnostics
map("n", "<leader>ae", [[<cmd>lua vim.diagnostic.setqflist({severity = "E"})<CR>]]) -- all workspace errors
map("n", "<leader>aw", [[<cmd>lua vim.diagnostic.setqflist({severity = "W"})<CR>]]) -- all workspace warnings
map("n", "<leader>d", "<cmd>lua vim.diagnostic.setloclist()<CR>") -- buffer diagnostics only
map("n", "<F2>", "<cmd>lua vim.diagnostic.goto_next { wrap = false }<CR>")
map("n", "<S-F2>", "<cmd>lua vim.diagnostic.goto_prev { wrap = false }<CR>")

Running the metals doctor gives the following output:

## Metals Info
  - Metals Server version: 0.11.8
  - Build server currently being used is sbt v1.7.1.
  - Metals Java: 17.0.4 from OpenJDK BSD Porting Team located at /usr/local/openjdk17

These are the installed build targets for this workspace. One build target corresponds to one classpath. For example, normally one sbt project maps to two build targets: main and test.

## Build Targets

### comparison
  - target type: Scala 3.1.3
  - compilation: ✅ 
  - diagnostics: ✅ 
  - interactive: ✅ 
  - semanticdb: ✅ 
  - debugging: ✅ 
  - java: ⚠️ 

### comparison-it
  - target type: Scala 3.1.3
  - compilation: ✅ 
  - diagnostics: ✅ 
  - interactive: ✅ 
  - semanticdb: ✅ 
  - debugging: ✅ 
  - java: ⚠️ 

### comparison-test
  - target type: Scala 3.1.3
  - compilation: ✅ 
  - diagnostics: ✅ 
  - interactive: ✅ 
  - semanticdb: ✅ 
  - debugging: ✅ 
  - java: ⚠️ 

### comparison-build
  - target type: sbt 1.7.1
  - compilation: ✅ 
  - diagnostics: ⚠️ 
  - interactive: ✅ 
  - semanticdb: ✅ 
  - debugging: ❌
  - java: ⚠️ 
  - recommendation: Diagnostics and debugging for sbt are not supported currently.

[ckipp01]

Hey @jan0sch thanks for the report. Completions in Scala 3 should work the same as when on Scala 2. Nothing from your setup looks out of place, so it should work the same. If you do a :MetalsToggleLogs do you see anything funky? Also is this happening for you on a minimal project?

[ckipp01]

The status bar stuff works.

Ok, so then your config is being taken into account.

[jan0sch]

Weird, I just kicked out everything from init.lua except nvim-lspconfig, nvim-metals and plenary resulting in the behaviour staying the same (Option 'omnifunc' not set).

Maybe I have to nuke my whole nvim config folders and caches and start from scratch after all. :-(

Or I just try to fiddle with some "autocomplete plugin", any recommendations for a good one?

[ckipp01]

A lot of users (including myself) use https://github.com/hrsh7th/nvim-cmp.

[jan0sch]

Thanks, I gave it a try and indeed it includes the metals autocomplete. But I remembered why I have removed all the autocomplete plugins in the first place (despite of all the speed they feel slugish).

So I will try to make it work with default nvim completion. If I succeed I'll report my findings/solution here.

[jan0sch]

I was unable to get autocomplete working without nvim-cmp but at least I could configure it to only trigger completion upon key press (c-n): hrsh7th/nvim-cmp#1199

Thanks a bunch for your help and for nvim-metals of course. :-)