Ensime TNG nvim lspconfig

config.lua

local configs = require 'lspconfig.configs'
local lspconfig = require 'lspconfig'

-- Check if the config is already defined (useful when reloading this file)
if not configs.ensime then
  configs.ensime = {
    default_config = {
      cmd = {
        'java', '-jar', os.getenv("HOME") .. '/.cache/ensime/lib/ensime-lsp.jar'
      },
      filetypes = {'scala'},
      root_dir = function(fname)
        return lspconfig.util.find_git_ancestor(fname)
      end,
      settings = {}
    }
  }
end

-- call `setup()` to enable the FileType autocmd
require'lspconfig'.ensime.setup {}

since ensime-tng is project agnostic, I think it's safe to set the project root to / or any other wildcard that neovim supports.

since ensime-tng is project agnostic

Could you explain a bit more about what you mean by this? If it's project agnostic how does it know what sources for example "belong" to a project?

@ckipp01 check out the README for details. The compiler plugin extracts the build information, and it can reconcile all the open files that belong to the same compilation module. The build tool's definition of the project is irrelevant.