$msCompile problem matcher has issues with wrapped lines

[tvardero]

Duplicate: #85839, #127073.

Ran using terminals: Git Bash, Command Prompt, Power Shell. All the same.
Problem matcher: $msCompile

I don't have any terminal related settings in settings.json (except for default terminal).

Does this issue occur when all extensions are disabled?: Yes (even with disabled Omnisharp)

• VS Code Version: 1.67.2
• OS Version: Win10 x64 build 19044.1706 (I'm not able to update to Win11)

Steps to reproduce are all the same as in duplicate issues:

1. Create a task outputting multiple long lines that will get wrapped in the terminal
2. Run the task with a limited space for the terminal
3. Observe the matched problems

Any workarounds for now?

[alexr00]

@meganrogge in case you want to take a look at this.

[Gruntfuggly]

There are two workarounds (that are horrible)

1. Make your window wider
2. Make your font smaller

[TemporalOroboros]

This still occurs as of vscode 1.79.2.
So long as this only effects the error description its actually not so bad: Omnisharp can point it out when you get to the file. If it breaks the error filepath it can make it hard to hunt down where the error occurs. (The link reported by the problem matcher directs to a file that does not exist.) The worst case is where it breaks the '(line, column)' part of the error message. In that case it straight up does not report the error.

In this case the content of errors.txt was manually copypasted from the terminal during compilation as containing a match for ^C:[^:]+\s.

[jtsom]

Still an issue.

See: dotnet/vscode-csharp#6309

[JulianJvn]

• Same problem with a shell task (calling pydocstyle) running in cmd.exe using a custom problem matcher (regular expression ^ (D\\d+): (.*)$).
• Possibly related to Wrapped lines lead to wrong problems #32042.

[TryerGit]

Still an issue with with >= 1.80.0 version it seems. I raised a discussion on this over at cpptools also:
microsoft/vscode-cpptools#11759

[scrappyCoco]

I have found the cause of this problem. My first variant of tasks,json was like this:

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "build dotnet example",
            "command": "dotnet",
            "type": "shell",
            "args": [
                "build",
                "/property:GenerateFullPaths=true",
                "/consoleloggerparameters:NoSummary",
                "${workspaceFolder}\\MyProject.csproj"
            ],
            "problemMatcher": "$msCompile"
        }
    ]
}

With that config I had had truncated messages inside Problems tab. Then I added the value ForceNoAlign (don't align the text to the size of the console buffer) to parameter consoleloggerparameters and it solved the problem. True example:

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "build dotnet example",
            "command": "dotnet",
            "type": "shell",
            "args": [
                "build",
                "/property:GenerateFullPaths=true",
                "/consoleloggerparameters:'ForceNoAlign;NoSummary'",
                "${workspaceFolder}\\MyProject.csproj"
            ],
            "problemMatcher": "$msCompile"
        }
    ]
}

For now, it does not matter what the size of the window. All messages in the Problems tab are not truncated.

[JulianJvn]

That solution only applies to dotnet and msbuild tasks.

[hvbtup]

That solution only applies to dotnet and msbuild tasks.

Yes, I think we need a more general solution. For example, in my case I'm using PMD and other command line programs to generate messages.

[Celthi]

A general solution is to enable the problem matchers to consume the output inside a file.
Thus the task save the outputs into a file, later the problem matchers reads the output from the file. Something like
{
"command": " command > a_file.txt 2>&1",
"problemMatcher": {
"source": "a_file.txt"
}