Unnecessary (?) completions on "do|"

[teamon]

It seems that do| triggers completions and when hitting enter it will insert defoverridable instead of going to the next line. Since do is a keyword I think it should skip completions (ideally go to the next line and insert end if needed)

[teamon]

This is what ElixirLS shows:

and hitting enter will move the cursor to the next line and insert the missing end

[mhanberg]

You hit d with triggers the completions, then then the editor fuzzy filters them down to show what's in the screenshot.

Is this zed? I'm not sure why it would auto select the first option, I imagine that has other consequences.

Orthogonally, can probably add do as a completion candidate.

[teamon]

This one is from vscode. ElixirLS seems to prioritize do as a reserved keyword and selects it as the first option.

Can I can test something else or get some logs to see why this happens?

[mhanberg]

To clarify, what are you wanting to test? Why VScode is selecting the completion item?

[teamon]

Well just anything I can do to help :)

[mhanberg]

Gotcha, well I'll clarify:

• do is not a completion item in Next LS, so it not appearing is expected (this can be changed if desired), nothing to debug.

• VScode auto selecting the first candidate is not in my control, there might be settings around it, but I don't use it so I'm unaware.

[mhanberg]

Changing the second option is probably what you want.

[teamon]

I've checked with Zed and there completions are shown on d, then hidden on do and then shown again on do<any other character>.

Thanks for all the help, I'm going to close this for now.