Open wobakj opened 1 month ago
@wobakj I believe this was caused by a change made to the cwd that is used for child processes.
I was mistaken by my previous comment. The change I made only affected the cwd of the cpptools-srv process and not clang-format...I don't know what change could have caused a change to clang-format (i.e. I looked and didn't see any).
Too bad. Is there anything I can do help to diagnose the cause?
@wobakj Yeah, which version was the last version that worked and the 1st version that stopped working? Can you confirm 1.19.1 (November) was working and 1.19.2 (January) was not working? i.e. see https://github.com/microsoft/vscode-cpptools/releases?page=2 .
Environment
Bug Summary and Steps to Reproduce
Bug Summary: When a custom default terminal is defined for windows, and clang-format is configured as formatter, it is not executed within the terminal. As a result, custom clang-format executables, which require an extended
PATH
to find all DLLs, will fail at DLL load.Until December 2023, this was working, but I could not find anything related in the changelogs.
It is not possible to work around this by using
set PATH=...&&
in the value ofC_Cpp.clang_format_path
because it is put into quotes when executed by vscode and thus not recognized as mutliple commands.Steps to reproduce:
settings.json
as below.h
or.cpp
fileExpected behavior: clang-format is executed in the specified default terminal, enabling custom builds.
Configuration and Logs
Other Extensions
Disabled all extensions except for ms-vscode.cpptools
Additional context
No response