For code highlighting I use treesitter.
andrzej-mag
stefanluptak
Thanks a lot. I was confused by that tutorial, because it showed Elixir code that was syntax highlighted and didn’t mention the fact that I have to install some extra plugin for that. 
0
hauleth
Vim do not provide Elixir highlighting OOtB so you either need to use TreeSitter in NeoVim or use “classic” syntax definition from vim-elixir in Vim or NeoVim.
2
natdm
Hey everyone. Converting my configs from vim to neovim with Lua.
As far as elixir experience goes, I don’t get very accurate references, even though it’s in the list of references in elixir_sense lsp. Im for sure getting a better experience with the coc-nvim plugin, but I’ve decided to switch – the programmable lsp is pretty amazing and is the clear path forward. I plan on testing the lsp, coc, and nvim-lsp to see what the deal is and if I can help in any way.
For anyone who’s converted to nvim-lsp, maybe throw out what issues you’re having on the supported features (from the list of provided functionality).
A plug for a library that I didn’t write, but just committed some elixir queries to, is nvim-treesitter-textobjects, allowing you to make text-objects out of the supported ts-capture (hopefully it auto-merges tonight). I’ve made captures for parameters, comments, and a few more things.
0
pCosta99
Hey, I’ve been using neovim LSP for a while now too. Just recently discovered/decided to try using a dialyzer, but I failed to make it work just by enabling the correct flags. Has anyone had any success with that so far?
0
te_chris
I’ve just decided to jump back into vim (nvim to be exact) after a few years of vscode. I’ve gone with NVChad as a base config as I didn’t want to have to start from scratch. Mostly it all seems fine but I’m not seeing any completions from the Ex LSP. According to my LspInfo it’s running, but I’m at a bit of a loss.
I installed it using Mason and configured it as so:
lspconfig.elixirls.setup {
on_attach = on_attach,
capabilities = capabilities,
cmd = { "/Users/blah/.local/share/nvim/mason/packages/elixir-ls/launch.sh" }
}
Any help appreciated!
0
TunkShif
The elixirls is not attached to the current buffer, so it’s not actually running. Try execute :LspStart elixirls to first check if the lsp server can be started correctly.
2
te_chris
Thanks for that. That helped me trace the problen. I was using the wrong launch cmd, just for future reference. Should’ve been language_server.sh.
1
dfalling
I’ve just ported my old Neovim vimscript config to Lua, and the elixir-ls config was really tripping me up. I finally realized that using the ~/ alias in my cmd path was tripping it up. Hope this helps anyone else who comes across this.
require('lspconfig').elixirls.setup {
cmd = {"/Full/Path/to/elixir-ls/release/language_server.sh"},
on_attach = on_attach
}
0
dimitarvp
This is my LunarVim Elixir init section:
local root_pattern = require("lspconfig").util.root_pattern
require 'lspconfig'.elixirls.setup {
filetypes = { "elixir", "eelixir", "heex", "surface" },
root_dir = root_pattern("mix.exs", ".git") or vim.loop.os_homedir(),
cmd = { "/Users/dimi/bin/elixir-ls/release/language_server.sh" },
}
0