LSP strange behaviour on completion

[zoedsoupe]

I’m using helix v23.10 and this only happens with lexical-lsp and next-ls for elixir language.

I know that i can pres <ret> to confirm completion and tab and shift+tab to cycle trough completions list. However this happens when I try top confirm a lexical-lsp completion:

b130a364-bc8c-47d1-9c4a-76d7a73c74e6.mp4

[pascalkuthe]

what exactly is the issue here? I don't see anything wrong with that video?

[zoedsoupe]

When I “hover” trough a completion option, it inputs on the buffer a “snippet” for the argumetns function, like the String.trim/1 function as:

String.trim(string)

However when i press <ret> the resulting completion is

# cursor inside parens
String.trim()

For 1 arity functions that’s not a problem, however for 2 or more it results:

# writes “,” to buffer but not argument names?
String.at(, ,)

the acceptance of the completion would also benefit the struct fields completion, like:

# showed by “hover” on completion option:
%MYStruct{foo: foo}

# inserted on acceptance:
%MyStruct{foo: }

it’s seems kinda confusing to me 🤔

[pascalkuthe]

those are snippept placeholder. They are supposed to be removed automatically according to the lsp spec. In some languages they can be useful to keep but not in others. Once we support placeholders properly we can make them work like vscode where you can keep the content by hitting tab again (in vscode they disappear as soon as you start typing) but that is not implemented yet.