-
-
Notifications
You must be signed in to change notification settings - Fork 83
[Enhancement] Pass arguments to lsp #446
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
Comments
The command |
Please consider #447 when adding support for this feature. |
@Yakkhini you could seemingly work around this by defining your own Bash script like so:
and then specifying the path to your Bash script as the value for the |
It seems like a good idea. ;) I will give it a try later. As now, I've decided setting verible language server experimental feature to false and use this plugin with CHIPS ALLIANCE' official plugin together. Thanks! |
Describe the bug
I'm using verible-verilog-ls as my SystemVerilog Language Server and I found that there is no options to pass arguments for verible lsp or other language servers. I found that the plugins source code has wrote an interface for passing arguments to language servers in
src/extensions.ts
, functionsetupLanguageClient()
, argumentserverArgs
but with some reason it isn't been exposed as an setting option.I want to implement (or modify) this function to read lsp arguments from settings and pass to language server. Verible lsp working is enough for me, but it seems like modify the function would effects other lsp. So there is any plan to implement this feature or any reason not to implement it?
If the maintainer agree for implementing the feature, I would like contribute to this plugin.
(Plus, pass argument in path straightly not work, at least the verible lsp can't work. I will put relative info below.)
Environment (please complete the following information):
Steps to reproduce
Steps to reproduce the behavior:
Log
Expected behavior
Verible lsp works with custom rules.
Actual behavior
Couldn't create connection to server.
The text was updated successfully, but these errors were encountered: