microsoft / microsoft/vscode-cpptools

C_Cpp>Vc Format>Indent:Preprocessor Setting Not Applied in Nested Scenarios

Open
#11,428 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Feature: Code Formatting Language Service
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Environment
  • OS and Version: Windows11 22H2
  • VS Code Version: 1.82.0
  • C/C++ Extension Version: v1.17.5
  • If using SSH remote, specify OS of remote machine:
Bug Summary and Steps to Reproduce

1、when i set C_Cpp>Vc Format>Indent:Preprocessor to "none", but the Preprocessor(#define , #include...) always set to "leftmostcolumn"

2、When I use Doxygen to generate comments, the second line will automatically indent by one space.
image

3、how can i define the auto indent format like this?
image

Configuration and Logs
{
    "configurations": [
        {
            "name": "Win32",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "defines": [
                "_DEBUG",
                "UNICODE",
                "_UNICODE"
            ],
            "cStandard": "c17",
            "cppStandard": "c++17",
            "intelliSenseMode": "windows-msvc-x64"
        }
    ],
    "version": 4
}
Other Extensions

No response

Additional context

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 reproducing the nested preprocessor and Doxygen-comment indentation cases with the reported VS Code C/C++ extension configuration. No source file or test is identified in the issue; done means determining why the preprocessor setting is ignored and making the requested indentation behavior consistent in both scenarios.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.