Support Elixir 1.18

[scohen]

Support 1.18.

Test failures were due to old versions of beam files hanging around. This quiets warnings and all tests pass locally.

Fixes #846

[Moosieus]

I keep seeing errors pop up, seemingly due to some issue with elixir_sense. Logs here

[scohen]

@Moosieus Updated elixir_sense. That should take care of the error you're seeing (I was told it's benign, but yes, it's gross).

[Moosieus]

I was told it's benign, but yes, it's gross

That about sums up my experience. I've pulled the update, gonna work with it and see if anything else crops up.

[Moosieus]

That seems to have done the trick

[Moosieus]

Been using without issues, and the code looks good on review.

[trashhalo]

Not sure if this is an existing lexical thing and I just need to delete some file. but been getting issues with use statements where all of them are mad. including ones not from deps. like root app. use Standd, :controller.

[DnOberon]

Is this kinda dead in the water? I know they're working on the unified LS - but is lexical still receiving updates in the meantime?

[rdlu]

Is this kinda dead in the water? I know they're working on the unified LS - but is lexical still receiving updates in the meantime?

I was waiting this pr to be merged as well, but then I installed manually using the 1.18 branch. I went back to next-ls for a while, but this is much faster on my setup.

Cloning, switching to support_1_18 branch and then mix package --path ~/.local/bin/lexical was less painful than I imagined.

It works with my lazyvim/neovim setup: https://github.com/rdlu/dotfiles/blob/main/lazyvim/.config/nvim/lua/plugins/elixir.lua

Also with zed editor I just symlinked to ~/.local/share/zed/extensions/work/elixir/lexical-v0.7.x

[garlandcrow]

Is this kinda dead in the water? I know they're working on the unified LS - but is lexical still receiving updates in the meantime?

I was waiting this pr to be merged as well, but then I installed manually using the 1.18 branch. I went back to next-ls for a while, but this is much faster on my setup.

Cloning, switching to support_1_18 branch and then mix package --path ~/.local/bin/lexical was less painful than I imagined.

It works with my lazyvim/neovim setup: https://github.com/rdlu/dotfiles/blob/main/lazyvim/.config/nvim/lua/plugins/elixir.lua

Also with zed editor I just symlinked to ~/.local/share/zed/extensions/work/elixir/lexical-v0.7.x

hmm I tried your config (I'm also using lazyvim so there wasn't really much difference except the build path) and built from latest commit on this branch, but it wouldn't run so seems some issues still. FWIW, I made sure to build on the same version of elixir/otp as I ran in the test repo. elixir 1.18.2 and otp 27.2.2

My lexical.log attached.
test.log

[rdlu]

Is this kinda dead in the water? I know they're working on the unified LS - but is lexical still receiving updates in the meantime?

I was waiting this pr to be merged as well, but then I installed manually using the 1.18 branch. I went back to next-ls for a while, but this is much faster on my setup.
Cloning, switching to support_1_18 branch and then mix package --path ~/.local/bin/lexical was less painful than I imagined.
It works with my lazyvim/neovim setup: https://github.com/rdlu/dotfiles/blob/main/lazyvim/.config/nvim/lua/plugins/elixir.lua
Also with zed editor I just symlinked to ~/.local/share/zed/extensions/work/elixir/lexical-v0.7.x

hmm I tried your config (I'm also using lazyvim so there wasn't really much difference except the build path) and built from latest commit on this branch, but it wouldn't run so seems some issues still. FWIW, I made sure to build on the same version of elixir/otp as I ran in the test repo. elixir 1.18.2 and otp 27.2.2

My lexical.log attached. test.log

By looking at you log you are using Windows, am I right?

I'm not sure if I can help, I'm exclusively using Linux since eons ago (sometimes macos)

But sometimes my neovim or zed editor get stuck, the suggestions stop appearing, gd stops working, etc.

My workaround to avoid this is whenever there are major changes to versions I prefer to clean everything that was built. I have this in my justfile
that I use for my projects, then I mix deps.get again to start from a clean build state:

clean-dev:
  rm -rf ./.elixir_ls ./_build ./deps ./.elixir-tools
  find . -name "*.beam" -exec rm -f {} \;

[garlandcrow]

Is this kinda dead in the water? I know they're working on the unified LS - but is lexical still receiving updates in the meantime?

I was waiting this pr to be merged as well, but then I installed manually using the 1.18 branch. I went back to next-ls for a while, but this is much faster on my setup.
Cloning, switching to support_1_18 branch and then mix package --path ~/.local/bin/lexical was less painful than I imagined.
It works with my lazyvim/neovim setup: https://github.com/rdlu/dotfiles/blob/main/lazyvim/.config/nvim/lua/plugins/elixir.lua
Also with zed editor I just symlinked to ~/.local/share/zed/extensions/work/elixir/lexical-v0.7.x

hmm I tried your config (I'm also using lazyvim so there wasn't really much difference except the build path) and built from latest commit on this branch, but it wouldn't run so seems some issues still. FWIW, I made sure to build on the same version of elixir/otp as I ran in the test repo. elixir 1.18.2 and otp 27.2.2
My lexical.log attached. test.log

By looking at you log you are using Windows, am I right?

I'm not sure if I can help, I'm exclusively using Linux since eons ago (sometimes macos)

But sometimes my neovim or zed editor get stuck, the suggestions stop appearing, gd stops working, etc.

My workaround to avoid this is whenever there are major changes to versions I prefer to clean everything that was built. I have this in my justfile that I use for my projects, then I mix deps.get again to start from a clean build state:

clean-dev:
  rm -rf ./.elixir_ls ./_build ./deps ./.elixir-tools
  find . -name "*.beam" -exec rm -f {} \;

No worries, was just posted in case this helps a maintainer, I'm more than used to elixir tools being broken and unusable, so just check in from time to time to see if they work in neovim (spoiler, they never do). I'm running macos, super standard nothing special, default everything with neovim/lazynvim. Nothing ever works, its cool ✌🏼