Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add support for slangd #2907

Merged
merged 1 commit into from
Nov 20, 2023
Merged

feat: add support for slangd #2907

merged 1 commit into from
Nov 20, 2023

Conversation

theHamsta
Copy link
Member

@theHamsta theHamsta commented Nov 19, 2023

slangd is the language server for slang, a shader language that extends HLSL with additional features.

The filetype shaderslang is a invention of myself, but I plan to also use it for a tree-sitter parser nvim-treesitter/nvim-treesitter#5659 and a TBD PR to vim for filetype detection. shaderslang is used because Vim/Neovim already has support for a filetype called slang which I assume is for https://en.wikipedia.org/wiki/S-Lang with extension *.sl while shaderslang uses *.slang. The language server also works with regular hlsl https://learn.microsoft.com/en-us/windows/win32/direct3dhlsl/dx-graphics-hlsl / https://de.wikipedia.org/wiki/High_Level_Shading_Language (which would also require a PR to be detected by Vim/Neovim). I'm not aware of any Vim plugins for slang.

Please let me know when this PR should remain in draft status until the Vim PR is completed.

`slangd` is the language server for [slang](https://github.com/shader-slang/slang),
a shader language that extends HLSL with additional features.
@glepnir
Copy link
Member

glepnir commented Nov 20, 2023

There is no order actually. There are many custom file types lsp here. just make sure filetype register (vim.filetype.add) before lspconfig load .

@glepnir glepnir merged commit e8842b9 into neovim:master Nov 20, 2023
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants