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
How to debug VSCode LS? #2127
Comments
I need to double check that all the formatting paramters are passed through properly. But for debugging, try to set the following environment variables, they will increase the loglevel.
Don't know if you can set environtment variables directly in VSCode, I usually just set them in the shell I start vscode, then they wil be inherited. |
I've updated the code to emit the command line at startup of the language server. This should help to see if the command line flags arrive where they should. You should be able to see them and restart vscode after updating the language server. Note, you don't need to set any environment variables as suggested earlier, it will always show up. If you watch the output, make sure that all the arguments start with double-dash. So it needs to look like |
Did it help ? |
Using VSCode 1.86.2
What activity failed
I can't get the plugin to obey any of the formatter settings. It looks like it's using the default "infer" state as I can get assignments to align, for example, if I manually insert spaces until it identifies what I'm trying to do.
So what is the correct format of the
verible.arguments
list insettings.json
? I've tried the following:I also tried with a space separated list and swapping the equals for a space. None of which worked nor caused any sort of error/warning in the log.
And obviously running the same commands from the command line
verible-verilog-formatter
does what I want.Logfiles
Here's the output of one of the log files. I didn't have a
verible.filelist
file initially (and saw errors) so created one but it had no effect.So could someone define the format expected within
settings.json
and then document it somewhere? And if that isn't the issue in this case, suggest how I can debug this further?Thanks.
The text was updated successfully, but these errors were encountered: