Replies: 1 comment
-
Agreed, I could see this being useful for things like I would suggest to also (or only) be able to override this on a per-language basis for more flexibility: [language-server.crates-lsp]
command = "crates-lsp"
[[language]]
name = "toml"
language-servers = ["taplo", { name = "crates-lsp", only-files = [ { glob = "Cargo.toml" } ] }] I think the easiest would be if that pattern would be a filter on the normally matched files for the language. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There are some issues reported around about Helix coupling heavily the LSP selection with the language
I'd like to suggest also allowing one to link a LSP to a file pattern using an option like
file-types
instead of only a language. That way a LSP could bedefined to be used in all files, like lsp-ai, or a markdown spell checker could be configured to use a specific language if the file
matches with
*.en.md
and one, like me, can have automatic spell checker configured in a simple way on a Hugo multi language project.Configuration example that should work:
Beta Was this translation helpful? Give feedback.
All reactions