You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Hover docs and go-to-definition for imported Kernel functions/macros not working in v0.6.0 #49
Describe the bug
After upgrading to 0.6.0 LSP features like go to definition, lookup documentation stoped working for Elixir standard library. It works fine for other parts of the code. It was working fine with earlier version of Dexter.
To reproduce
Configure Dexter in Neovim using vim.lsp.
Expected behavior
Features mentioned above should work for standard Elixir library
Hi @gsarwate, thanks for the issue! Could you provide a code sample that replicates what you're describing? I am unable to replicate the issue. Could you verify in your logs that Dexter reports finding your Elixir stdlib? I think that might be the issue.
Thanks @gsarwate, I'm still unable to replicate on my side in the Tidewave codebase. For example, go-to-definition on use Mix.Project in the mix.exs file works fine for me.
Can you enable debug in your config and send me the logs after attempting go-to-definition again?
@gsarwate I don't see any attempt at a go-to-definition in those logs. Could you attempt a few go-to-definitions in the problem areas and send the debug logs?
@gsarwate you'll need to be more specific with exactly what code is causing you problems, what you're hovering over, and what you expect to happen. A video would be helpful. I'm also running v0.6.0 on Tidewave Phoenix and am not having any issues doing go-to-definition and hover to Elixir standard library modules/functions.
changed the title [-]After upgrading to 0.6.0 LSP features do not work for standard Elixir libraries[/-][+]Kernel and SpecialForms hover docs and go-to-definition not working in v0.6.0[/+]on Apr 24, 2026
changed the title [-]Kernel and SpecialForms hover docs and go-to-definition not working in v0.6.0[/-][+]Kernel hover docs and go-to-definition not working in v0.6.0[/+]on Apr 24, 2026
changed the title [-]Kernel hover docs and go-to-definition not working in v0.6.0[/-][+]Hover docs and go-to-definition for imported Kernel functions/macros not working in v0.6.0[/+]on Apr 24, 2026
Thank you @gsarwate. Now I see what you're talking about. I did not even consider that people would want to be doing go-to-definition on things like defmodule, so I never tested for it. Our previous support for some of these forms was more a consequence of how we parsed things rather than an intentional decision. However, you're right that there is indeed a regression here. This should be a relatively simple fix, so I'll see about adding this back.
Activity
JesseHerrick commentedon Apr 23, 2026
Hi @gsarwate, thanks for the issue! Could you provide a code sample that replicates what you're describing? I am unable to replicate the issue. Could you verify in your logs that Dexter reports finding your Elixir stdlib? I think that might be the issue.
JesseHerrick commentedon Apr 23, 2026
To show the latest logs:
gsarwate commentedon Apr 24, 2026
Log from ~/.local/state/nvim/lsp.log:
Example code:
I tried go to definition from mix.exs file's
defmoduleand other macros. The mix.exs file is standard one and this particular file is part of tidewave-phoenix project: https://github.com/tidewave-ai/tidewave_phoenix/blob/main/mix.exsThis worked fine with same Elixir version with previous version (0.5.x) of Dexter.
My Neovim LSP config:
JesseHerrick commentedon Apr 24, 2026
Thanks @gsarwate, I'm still unable to replicate on my side in the Tidewave codebase. For example, go-to-definition on
use Mix.Projectin themix.exsfile works fine for me.Can you enable
debugin your config and send me the logs after attempting go-to-definition again?gsarwate commentedon Apr 24, 2026
Here are the logs after enabling debug for Dexter:
gsarwate commentedon Apr 24, 2026
Here are additional details related to Dexter from
checkhealth vim.lspoutput:JesseHerrick commentedon Apr 24, 2026
@gsarwate I don't see any attempt at a go-to-definition in those logs. Could you attempt a few go-to-definitions in the problem areas and send the debug logs?
gsarwate commentedon Apr 24, 2026
Here are logs from a few attempts. The last one shows the success which is going to internal Module (Tidewave.Application). Others failed:
JesseHerrick commentedon Apr 24, 2026
@gsarwate you'll need to be more specific with exactly what code is causing you problems, what you're hovering over, and what you expect to happen. A video would be helpful. I'm also running v0.6.0 on Tidewave Phoenix and am not having any issues doing go-to-definition and hover to Elixir standard library modules/functions.
gsarwate commentedon Apr 24, 2026
Here are the details of what works and what does not in the above mentioned mix.exs file.
When it does not work, I get message "No locations found"
Go to definition did not work:
Go to definition works:
Log for all the actions:
[-]After upgrading to 0.6.0 LSP features do not work for standard Elixir libraries[/-][+]Kernel and SpecialForms hover docs and go-to-definition not working in v0.6.0[/+][-]Kernel and SpecialForms hover docs and go-to-definition not working in v0.6.0[/-][+]Kernel hover docs and go-to-definition not working in v0.6.0[/+][-]Kernel hover docs and go-to-definition not working in v0.6.0[/-][+]Hover docs and go-to-definition for imported Kernel functions/macros not working in v0.6.0[/+]JesseHerrick commentedon Apr 25, 2026
Thank you @gsarwate. Now I see what you're talking about. I did not even consider that people would want to be doing go-to-definition on things like
defmodule, so I never tested for it. Our previous support for some of these forms was more a consequence of how we parsed things rather than an intentional decision. However, you're right that there is indeed a regression here. This should be a relatively simple fix, so I'll see about adding this back.