Metals command not available

[voodoojunk]

Hi.

init.lua requires the scala module:

require('scala')

My lua/scala.lua looks like this:

vim.o.shortmess = string.gsub(vim.o.shortmess, 'F', '') .. 'c'

local ft = { "scala", "sbt", "java" }
local metals_config = require("metals").bare_config()

metals_config.settings = {
    showImplicitArguments = true
}
--- statusBarProvider
metals_config.init_options.statusBarProvider = "off"

-- make sure the correct capabilities for snippets are set
metals_config.capabilities = require("cmp_nvim_lsp").default_capabilities()

local nvim_metals_group = vim.api.nvim_create_augroup("nvim-metals", { clear = true })
vim.api.nvim_create_autocmd("FileType", {
pattern = ft,
callback = function()
  require("metals").initialize_or_attach(metals_config)
end,
group = nvim_metals_group,
})

The installation of nvim-metals was successful (I use Vim-Plug for package management .... yes, I know...)
After the installation, I can see all the commands in the help page when running :h MetalsCommands, but the command are not actually accessible. For example :MetalsInstall returns:

 E492: Not an editor command: MetalsInstall

Trying to autocomplete commands Metals* doesn't show anything either....

I've also tried the absolute minimal config which yielded the same results:

vim.cmd([[autocmd FileType scala,sbt lua require("metals").initialize_or_attach({})]])

What am I missing?

[ckipp01]

Hey @voodoojunk, the error makes it seem like Metals isn't actually attached. When you see this can you try to do :lua vim.print(vim.lsp.get_clients()), and see if you have a client actually attached? If that table is empty, then they issue is with the autocmd.

[ckipp01]

Did you try with a standalone config file and now and passing it in directly to nvim when starting?

[voodoojunk]

Not sure what you mean so I tried this:

custominit.lua:

vim.cmd('source ~/.config/nvim/customplugins.vim')
require("metals").initialize_or_attach({})

customplugings.vim:

call plug#begin()
Plug 'preservim/nerdtree'
Plug 'neovim/nvim-lspconfig'
Plug 'hrsh7th/cmp-nvim-lsp'
Plug 'hrsh7th/cmp-buffer'
Plug 'hrsh7th/cmp-path'
Plug 'hrsh7th/cmp-cmdline'
Plug 'hrsh7th/nvim-cmp'
Plug 'hrsh7th/cmp-vsnip'
Plug 'hrsh7th/vim-vsnip'
Plug 'nvim-telescope/telescope.nvim'
Plug 'vim-airline/vim-airline'
Plug 'vim-airline/vim-airline-themes'
Plug 'ryanoasis/vim-devicons'

" --- metals
Plug 'nvim-lua/plenary.nvim'
Plug 'j-hui/fidget.nvim'
Plug 'scalameta/nvim-metals'

call plug#end()

and then started nvim with vim -u custominit.lua. No bueno....

Also tried creating a custominit.vim:

call plug#begin()
Plug 'preservim/nerdtree'
Plug 'neovim/nvim-lspconfig'
Plug 'hrsh7th/cmp-nvim-lsp'
Plug 'hrsh7th/cmp-buffer'
Plug 'hrsh7th/cmp-path'
Plug 'hrsh7th/cmp-cmdline'
Plug 'hrsh7th/nvim-cmp'
Plug 'hrsh7th/cmp-vsnip'
Plug 'hrsh7th/vim-vsnip'
Plug 'nvim-telescope/telescope.nvim'
Plug 'vim-airline/vim-airline'
Plug 'vim-airline/vim-airline-themes'
Plug 'ryanoasis/vim-devicons'

" --- metals
Plug 'nvim-lua/plenary.nvim'
Plug 'j-hui/fidget.nvim'
Plug 'scalameta/nvim-metals'

call plug#end()

autocmd FileType scala,sbt lua require("metals").initialize_or_attach({})

then started, Nvim with vim -u custominit.vim. Also no luck...

[ckipp01]

Yea, what I meant was using -u configFile.lua or something, but it seems that also didn't work. Honestly, I have no idea. I haven't seen something like this reported before and without having any sort of info or logs or more details about what is happening, then I'm not sure. One other place to possibly look would be in your cache dir. nvim-metals should have a log file there that if it is getting started at all, it should log. For example on mac mine is located at ~/.cache/nvim/nvim-metals/nvim-metals.log

[voodoojunk]

Well ... no such luck. The log file doesn't exist (though the ~/.cache/nvim/nvim-metals dir does)
I guess I'll have to try to install the language server manually and start it via nvim-lspconfig
I'm not a scala developer. I just need to debug some code once in a while (mostly Apache Spark) so I just need the basic stuff like jump to definition, etc...
Hopefully working with lspconfig would suffice for that

Thanks again for all your help :-)

[voodoojunk]

Update - yeah.... installed metals server manually and using nvim-lspconfig to start it - works fine...
Thanks again...