Show the source of the active compilerPath in C/C++ configuration

Abierto
#14,863 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript, vscode

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
6.2k
Forks
1.7k
Merge medio
1 d 17 h
PR fusionados (30 d)
12

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/vscode-cpptools

Todos los issues de microsoft/vscode-cpptools

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.