Closed TimeTravelPenguin closed 3 months ago
lsp in neovim doesn't take responsibility to toggle comments, so it is probably not an issue that should report to lsp. The error "Option 'commentstring' is empty." could be a hint to update Neovim's language configuration for typst.
Thanks for your response. I have been looking into it, but progress is slow since I don't fully understand everything about neovim.
The error "Option 'commentstring' is empty." could be a hint to update Neovim's language configuration for typst.
As far as I can tell, I have everything up to date. Is there anything immediate that I can do to look further into this?
Thanks
I can confirm that I do not have typst's ftplugin file for some reason. It appears to have been added to the nvim repo 3 weeks ago, so if it was released with nvim 10.1, I am unsure why I do not have it.
Ok, it seems it was a nightly release. Apon adding these files to my vim directory, things are working as expected. I suppose they will be released with the next stable build.
Thanks for your time.
Describe the bug I am not 100% sure if this is a bug or if I have messed up my neovim setup, so I hope this is the correct place to ask.
I am using NvChad, and my setup doesn't follow the install guide of tinymist exactly. I am relatively new to nvim, too.
I believe I have things working, but for some reason, I cannot seem to get my
space+/
keybind to toggle comments. I get an error:Option 'commentstring' is empty.
In my lspconfig.lua configuration file, I have:
I do not use mason-lspconfig, so this is my best attempt to make it work with only mason and lspconfig. If anyone can confirm whether or not my setup is the root cause, I would be greatly appreciative.
Thanks
Package/Software version:
tinymist extension version:
v0.11.1
.