microsoft / microsoft/vscode-cmake-tools

[Feature] More Effective Logging Level Setting

Open
#5,002 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
1.7k
Forks
546
Avg merge
2d 16h
Merged PRs (30d)
32

Description

### Request Overview

Hi,
the extension seems to log a lot of info by default into the Output panel in VSCode. Since that panel kind of breaks VSCodes windowing and tiling systems (automatically pops up, can't be disabled, always fixed to the side or bottom) I wanted to reduce the amount of things that get logged, optimally to just compile errors. CMake Tools actually provides a setting for this under `cmake.loggingLevel` (defaults to info). However the logging level of messages on the `CMake/Build` channel seems to be totally borked. A failed build is a "warning" and the actual compilation errors are "info", just like all the usual spam. I would have expected "error" to refer to cmake errors, build failures/compilation errors, "warning" maybe to a lower class of problems. But as it stands this setting doesn't solve my issues.

Am I missing a setting to get this desired behavior?

### Additional Information

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the cmake.loggingLevel setting and the messages emitted on the CMake/Build channel in the VS Code Output panel. Trace how build failures and compilation errors are assigned logging levels, then verify that the error setting shows those failures while suppressing routine informational output.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, typescript, vscode
Domain
build-system, developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.