Łukasz Samson

Thanks for letting us know @ghuntley. We need to setup an org account

Docs has been reworked since this was opened

> > There has been discussions about using compilation tracers. With compilation tracers, you will always know if a macro expands to `def`, so you can track all definitions. But...

Do anyone have a simple project that reproduces this reliably?

@brianmay I cannot reproduce this on current master using your repo.

I'm convinced that big part of that errors was a duplicate of https://github.com/elixir-lsp/elixir-ls/issues/120. This bug is fixed in https://github.com/elixir-lsp/elixir-ls/commit/031bd0a7246dc7f6d6e1077a975b55b2110f209c which will be part of 0.12 release. I'm going to close...

I'm going to close that as there is no consensus on how to approach that

Fixed in https://github.com/elixir-lsp/elixir-ls/commit/e4576def20c479dc7be7cc7e6079d017cb980c98 and released in v0.11

@RobertYost my guess is nvim-lsp is sorting items differently or not respecting the `preselect` flag...

2 years later I'm still not convinced, let's close this