rdlu
commented
2 months ago For the sake of completeness, my current neovim/lazyvim elixir config, but vscode is having the same:
return {
{
"elixir-tools/elixir-tools.nvim",
version = "*",
event = { "BufReadPre", "BufNewFile" },
config = function()
local elixir = require("elixir")
elixir.setup({
nextls = {
enable = true,
init_options = {
extensions = {
credo = {
enable = false,
},
},
experimental = {
completions = {
enable = true, -- control if completions are enabled. defaults to false
},
},
},
},
credo = {
enable = false,
},
elixirls = {
enable = false,
settings = require("elixir.elixirls").settings({
dialyzerEnabled = false,
enableTestLenses = false,
suggestSpecs = false,
}),
},
})
end,
dependencies = {
"nvim-lua/plenary.nvim",
},
},
{
"nvim-treesitter/nvim-treesitter",
opts = function(_, opts)
vim.list_extend(opts.ensure_installed, {
"elixir",
"heex",
"eex",
})
end,
},
{
"nvim-neotest/neotest",
optional = true,
dependencies = {
"jfpedroza/neotest-elixir",
},
opts = {
adapters = {
["neotest-elixir"] = {},
},
},
},
{
"nvimtools/none-ls.nvim",
optional = true,
opts = function(_, opts)
if vim.fn.executable("credo") == 0 then
return
end
local nls = require("null-ls")
opts.sources = vim.list_extend(opts.sources or {}, {
nls.builtins.diagnostics.credo,
})
end,
},
{
"mfussenegger/nvim-lint",
optional = true,
opts = function(_, opts)
if vim.fn.executable("credo") == 0 then
return
end
opts.linters_by_ft = {
elixir = { "credo" },
}
end,
},
{
"mhanberg/output-panel.nvim",
event = "VeryLazy",
config = function()
require("output_panel").setup()
require("which-key").register({
c = {
name = "Code",
o = { "<cmd>OutputPanel<cr>", "Open Output Panel" },
},
}, { prefix = "<leader>" })
end,
},
}
I'm again having some issues, with both neovim and vscode. The release version just stays forever initializing, even after doing the cleaning that I always do, but that is a separate issue.
To investigate the first issue, then I tried to clone the repo to run in dev mode with
just start, orjustthe burrito on my own (and copy tocp burrito_out/next_ls_linux_amd64 ~/.cache/elixir-tools/nextls/bin/nextls-custom, thenln -sthe custom tonextls. Then I had a different but highly reproducible issue with my system:I tried to update the exqlite inside mix.exs to
0.23.0thenmix deps.getThe message just changed to the new version:
So I can't investigate the other issue I'm having without loading the db.
My system:
some erl, elixir flags
I also tried removing the exqlite vars, or setting "use system" to 0. It indeed compiles by itself, but the result is the same.
my env cleaning script:
my project cleaning justfile script:
I updated the
.tools-versionsas well, then used mise to install the exact versions below, since the current elixir hashed version simply doesn't compile for me, but the one below is succesful:I have mise, but I also tried removing all mise erl/elixir installed versions, not loading mise at all, using the current system versions, the deps cache were installed to
~/.cache/mixinstead the usual mise/rtx/asdf locations to run my projects with neovim/vscode + nextls.Not sure if this is an burrito issue or what not, because just start with port 9000 causes almost the same issues. (the logs go to the next-ls folder instead my project folder, but the same error happens).
I don't have any issues with some side projects with phoenix that uses sqlite. That's why I have the exqlite flags, to accelerate the compiling of my side projects.
Any clues? Thanks!