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
Hey guys!
I installed Crystalline with :LspInstall crystal, this part works. :LspInfo :LvimInfo
However, nothing really happens. I don't get highlighting or other LSP features like autocomplete etc.
Thanks a lot!!
LunarVim version
release-1.3/neovim-0.9-d1c1bace
Neovim version (>= 0.9.1)
NVIM v0.9.5
Operating system/version
Linux / Fedora 39
Affected language servers
Crystalline
Steps to reproduce
Install Crystalline with :LspInstall crystal.
Create a test.cr file.
Write Crystal code.
Actual behavior
Nothing happens
Expected behavior
LSP works as intended, including code highlighting and auto-completion
support info
See screenshots from the OP.
logs
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered:
In LunarVim syntax highlighting is handled by nvim-treesitter which does not yet support the crystal filetype. The Crystalline README suggests to use the vim-crystal plugin.
It looks like the server is configured and launched correctly, but autocompletion does not work with nvim-lspconfig. This might be an issue with Crystalline itself: elbywan/crystalline#89
Problem description
Hey guys!
I installed Crystalline with
:LspInstall crystal
, this part works.:LspInfo
:LvimInfo
However, nothing really happens. I don't get highlighting or other LSP features like autocomplete etc.
Thanks a lot!!
LunarVim version
release-1.3/neovim-0.9-d1c1bace
Neovim version (>= 0.9.1)
NVIM v0.9.5
Operating system/version
Linux / Fedora 39
Affected language servers
Crystalline
Steps to reproduce
Install Crystalline with
:LspInstall crystal
.Create a
test.cr
file.Write Crystal code.
Actual behavior
Nothing happens
Expected behavior
LSP works as intended, including code highlighting and auto-completion
support info
See screenshots from the OP.
logs
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered: