Replies: 1 comment
-
Seems to be a problem with VSCode folks itself? See microsoft/vscode#150285 Would be great if a way out is possible. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am on Windows and call MSBuild like so in
tasks.json
:The
Terminal
tab displays the full error like so:C:\Users\TryerGit\Insync\TryerGit\GoogleDrive\research_programming\General_C_and_C++_Programming\VSCode_Windows\code\main.cpp(8,2): error C4996: 'scanf': This function or var
[the error message itself is split here via a newline thus the error message spans multiple lines]
iable may be unsafe. Consider using scanf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. [C:\Users\TryerGit\Insync\TryerGit\GoogleDrive\research_programming\General_C_and_C++_Programming\VSCode_Windows\.vscode\windows.vcxproj]
Now, when I then move to the
Problems
tab, this error is listed and clicking on it does take me to the file and line in question but the error message displayed is truncated like so:main.cpp -> 'scanf': This function or var cpp(C4996) [Ln 8, Col2]
You will notice that only the first 4 or 5 words of the actual complete error message is displayed. Is there a way to fix this so that the full error message is displayed? That is, with the default
$msCompile
problem matcher, it seems it is unable to catch multiline errors and hence displays only the first line. What changes should be made to the problem matcher so that it captures the full error message in theProblems
tab?Beta Was this translation helpful? Give feedback.
All reactions