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

Please allow suppression for messages related to vhdl_ls.toml #16

Open
nversluis opened this issue Mar 27, 2020 · 3 comments
Open

Please allow suppression for messages related to vhdl_ls.toml #16

nversluis opened this issue Mar 27, 2020 · 3 comments

Comments

@nversluis
Copy link

I would like to be able to use this extension without specifying a vhdl_ls.toml file.
In fact, the extension works very well without it being able to load the aforementioned file already.

However, every time I open VS Code, the following messages pop up:

Loaded Installation configuration file: /home//.vscode-server/extensions/hbohlin.vhdl-ls-0.3.0/server/vhdl_ls/0.15.0/vhdl_ls-x86_64-unknown-linux-gnu/bin/../vhdl_libraries/vhdl_ls.toml
[Error - 11:56:09 AM] Found no vhdl_ls.toml config file in the workspace root path: No such file or directory (os error 2)
[Warn - 11:56:09 AM] Found no library mapping, semantic analysis disabled, will perform syntax checking only
[Info - 11:56:09 AM] Opening file /home//path_to_file/file.vhd that is not part of the project

I would like to be able to suppress these messages, so they don't pop up every time I launch VS Code, since they don't impact what I am using the extension for, which is using it on a per-file basis.

@Bochlin
Copy link
Member

Bochlin commented Apr 1, 2020

It is the language server which sends these messages. As far as I know there is no way for the client to suppress messages from the server.

@nversluis
Copy link
Author

Would it then be possible to add an option to disable the language server output to VS Code entirely?
Honestly the only thing that bothers me is that the extension pops up the VS Code terminal every time I start it.

@levi-ee
Copy link

levi-ee commented May 18, 2022

It's a good VS Code extension, but I totally agree with @nversluis.
Did someone found a easy work around for that?

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

No branches or pull requests

3 participants