Skip to content

pane for displaying errors provided by the linter / static analyzer #205

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

Closed
jerabaul29 opened this issue Mar 11, 2021 · 3 comments
Closed
Labels
conclusion: declined Will not be worked on topic: code Related to content of the project itself type: enhancement Proposed improvement

Comments

@jerabaul29
Copy link

I am having the following "hello world" code that displays some warnings (red squiggles).

Screenshot from 2021-03-11 20-47-44

First, this is a bit surprising, as the code actually compiles fine and the error message (see later) is not really relevant. I wonder if the IDE misses some paths when looking for valid sources (I am using a custom core, from Sparkfun, for the Artemis boards).

My main question is: is there / can we get a separate pane or similar for listing all such errors? As of now it seems that the way for me to get more information is to hoover with the mouse over the squiggles (see screenshot). I wonder if for larger projects it would be easier to have a dedicated "linter and static analyzer warnings" pane, a la platformio IDE.

Screenshot from 2021-03-11 20-47-58

@jerabaul29 jerabaul29 added the type: enhancement Proposed improvement label Mar 11, 2021
@ubidefeo
Copy link

@jerabaul29
thanks for reporting this.
During development we used to have a stream from the Language Server available in output, but it proved to be confusing to testing users and mostly cluttering the UI.
You can enable logging from the language server from the preferences if you don't mind going through MegaBytes of messages in a .log file.
It is actually how we debug the LS.

image

@jerabaul29
Copy link
Author

Ok, thanks, going through MBs sounds a bit inconvenient. I will wait for a more mature 'error pane' then.

@ubidefeo
Copy link

thanks

@per1234 per1234 added topic: code Related to content of the project itself conclusion: declined Will not be worked on labels Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: declined Will not be worked on topic: code Related to content of the project itself type: enhancement Proposed improvement
Projects
None yet
Development

No branches or pull requests

3 participants