#Weird LSP on neovim
1 messages · Page 1 of 1 (latest)
seems like it's doing more of a grep
than giving me info
i get proper erroring and stuff when im not in insert mode its just the autocomplete is quite odd
I get the same wacky behaviour in VSCode. Sometimes it even doubles up when it does the completion too and makes it really awkward to work with. I'm hoping this gets fixed soon.
I've noticed this behavior as well. Sometimes I can replicate in vscode, sometimes I cannot. Pretty sure this relates to an old LSP issue on the project, allthough I do not have the link. Correct me if I'm wrong, but try typing out correctly, deleting part of it, then retrying again.
In the issue, it showed that it "fixes" itself on that specific line, and it seems to behave like that for me. Doing some more indepth testing tomorrow
How did you set this up? Anyone have gleam setup using nvchad?
yes I have
it automatically installs it for me , but I also just have it in my lspconfig
:LspInstall or :Mason if u dont have ur lspconfig
A weird thing I have come across, if u put in parentheses it seems to like it more
just seems to be bipolar
Don’t use Mason, doing so will means there is no link between the one in your editor and the one in your shell
The LSP is unfinished
you should probably raise an issue on mason-registry to get it removed in that case
I've tried but I don't understand it well enough to do it
I need help from someone who understands mason etc really
okay yep it downloads the entire language binary if installed via mason
https://github.com/mason-org/mason-registry/blob/2024-03-13-abrupt-tulip/packages/gleam/package.yaml
this probably was my source of problems during aoc, I just didn't bring it up because the lsp is unfinished like you mention 🙁
Could you add your context here please: https://github.com/mason-org/mason-registry/pull/3872
removing a package is not yet supported
https://github.com/mason-org/mason-registry/blob/936f3eb654d3b5deafbf51b969621bc062a5d7a3/packages/xo/package.yaml#L13 ?
actually those are different now that I read it, but we can deprecate the package and tell users to manually delete the binary and set it up via lspconfig
also its been a while since I've used gleam, might use it again and try out a proper setup in that
That sounds good
Has anyone got a config that will work on neovim properly then? Or is it just something that will need to be fixed on a patch later on?
A temporary fix could be a symlink, but I am unsure
This also happens in nvchad, but that could just be a weird config on my side unless osmeone can replicate
Usually that green text is not filled when the lsp is not doing anything, but in this case, it just stays there until the lsp does something.