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

VSCode Problem panel doesn't list all error messages #1158

Open
Joebeazelman opened this issue Jul 19, 2023 · 4 comments
Open

VSCode Problem panel doesn't list all error messages #1158

Joebeazelman opened this issue Jul 19, 2023 · 4 comments

Comments

@Joebeazelman
Copy link

When I build my project, I am able to see all the compiler error messages and warnings in the terminal. However, not all of the error messages are displayed in the problem panel of the IDE. This issue arises when the build generates a greater number of warning messages than error messages. For example, in my case, I receive a substantial amount of style warnings. There may be a limit imposed for each type of message shown in the problem panel. If this is the case, it must be a recent development, as it has not occurred before.

@reznikmm
Copy link
Contributor

Can you send error/warning messages as a raw file? I'll try to reproduce the issue with it.

@Joebeazelman
Copy link
Author

Is there a way of having it dump the errors and warnings into a file? The issue seems to occur only if there are a lot of style warning messages. It may be a VSCode problem, but it's worth investigating. Is there a way of turning off the style warning in Alire? Better yet, is there a way of getting LSP to fix using the format code command?

@reznikmm
Copy link
Contributor

reznikmm commented Aug 8, 2023

you can redirect output of gprbuild or alr build to a file in the terminal, like

gprbuild -P project.gpr > errors.log

You can turn off style warning -gnatyN compiler switch, I guess. To fix warning try to use gnatpp or Format file command in VS Code.

@Joebeazelman
Copy link
Author

This is related to issue #1160. The ALS is using a different toolchain than the one specified by ALR.

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

2 participants