Show the source of the active compilerPath in C/C++ configuration
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript, vscode
研究方向
Start by tracing how the extension resolves compilerPath from user and workspace settings, c_cpp_properties.json, and configuration providers. The issue does not name files or tests, so first locate those entry points and check how configuration sources are surfaced in the UI. Done means users can identify the active source and understand when multiple compiler path settings are configured.
由索引模型根據 Issue 內容生成。
描述
Feature Request
Is your feature request related to a problem?
When configuring the C/C++ extension, users may set different compiler paths in settings.json and c_cpp_properties.json.
It can be confusing for beginners to understand which setting is currently being used by IntelliSense, especially when the paths are different.
Describe the solution you'd like
I would like the C/C++ extension to display the source of the active compilerPath more clearly.
For example, the extension could show whether the active compiler path comes from:
- User Settings (
C_Cpp.default.compilerPath) - Workspace Settings
c_cpp_properties.json- A configuration provider
It would also be helpful to display a short explanation when multiple compiler path settings are configured.
Why is this feature useful?
This feature would help users understand their C/C++ configuration more easily, reduce confusion when troubleshooting IntelliSense, and make the extension more beginner-friendly.
- 主要語言
- TypeScript
- 星號
- 6.2k
- 分支
- 1.7k
- 平均合併
- 1 天 17 小時
- 30 天內合併 PR
- 12
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
microsoft/vscode-cpptools 的其他 Issue
-
Missing gcc __builtin_stdc_bit_width/floor/ceil signature makes intellisense wrongly report error 70未關閉
難度 2/5 1-3 小時 新手友好度 66/100
microsoft/vscode-cpptools#14874 ·
維護者通常 1 天內回覆
-
難度 3/5 1-2 天 新手友好度 65/100
microsoft/vscode-cpptools#14872 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 56/100
microsoft/vscode-cpptools#14871 ·
維護者通常 1 天內回覆
-
debugger
難度 4/5 3-5 天 新手友好度 45/100
microsoft/vscode-cpptools#14869 · 1 則留言 ·
維護者通常 1 天內回覆
-
Goto definition (F12) not working with (recursive) includes可能已有人在做 @Colengms 於 5 天前認領。 未關閉bug fixed Language Service
microsoft/vscode-cpptools#14868 · 2 則留言 · 1 個 reaction · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 microsoft/vscode-cpptools 的全部 Issue
相似的 Issue
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
難度 2/5 1-3 小時 新手友好度 68/100
openclaw/openclaw#199885 · 2 則留言 · 1 個 reaction ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 88/100
-
feature needs-triage
難度 2/5 1-3 小時 新手友好度 78/100
BoardGamesEmpire/board-games-empire-backend#1306 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 80/100
sequant-io/sequant#1689 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 80/100