Colen Garoutte-Carson

Hi @akmll . The behavior you're seeing very closely matches the behavior of https://github.com/microsoft/vscode-cpptools/issues/13622 , or what happens when msys64-hosted compilers cannot find DLLs they're dependent on. The C/C++ extension...

Hi @stertingen . Thanks for taking the time to suggest this. Since the project is using CMake, have you considered using the CMake Tools extension? CMake Tools provides configurations to...

@stertingen With CMake Tools, it's possible to specify an arbitrary CMakeLists.txt location, using `cmake.sourceDirectory`. Since it sounds like you're not using CMake Tools to build, you could use CMake Tools...

This appears to be a conflict with the extension `KylinIdeTeam.cppdebug`, which also registers `extension.pickNativeProcess`.

It looks like `editorconfig` 3.0.0 still references `one-ini`, which still uses `wasm`. My understanding is that the problem is with use of wasm in general conflicting with memory limits on...

Somewhat related: A warning could be displayed when an excessive number of files are discovered, prompting the user to set exclusions or explicitly set browse/include directories.

Hi @deepak1556 . Thanks for the heads-up. > If the batch script path may contain spaces, you will also need to wrap the path in quotation marks. I'd suggest being...

It looks like most of our calls to spawn or spawnSync already use `shell:true`. The rest appear to be in test code or code paths that aren't used. Code that...

Hi @M3hul-raj . I don't think arguments from `compilerArgs` are being ignored, generally speaking. It looks like the specific arguments you are using do not currently influence IntelliSense. We have...

Hi @debugee . We're working on a fix for this. In the meanwhile, it should be possible to work around the issue by configuring CMake to generate a `compile_commands.json` file...