Aleksander Kluczka

Full log (click to expand): ``` loggingLevel: Debug LSP: (received) cpptools/initialize (id: 1) LSP: (invoked) cpptools/initialize (id: 1) cpptools version (TypeScript): 1.21.3 cpptools version (native): 1.21.3.0 Autocomplete is enabled. Error...

I will also include screenshot of CMake Tools configuration UI and generated by CMake `compile_commands.json` as it seems relevant.  compile_commands.json ```json [ { "directory": "S:/Code/CPP/monoshot/build/src/render_interface_test", "command": "S:\\Environment\\Compilers\\mingw64_11.0.0_gcc_13.1.0_clang_16.0.5_msvcrt\\bin\\g++.exe -DGLFW_INCLUDE_NONE -DSPDLOG_SOURCE_LOCATION...

@sean-mcmanus I wonder why these MSVC include paths are taken into account... When I click on the source of the error:  ... I get to the cassert header itself,...

> It's possible those includePaths might be getting added from the system environment variables. I double checked system PATH and user PATH, I don't see anything added from Visual Studio...

Okay I pinned it down to the following setup: 1. Install Visual Studio 2022 (with MSVC compiler) 2. Install i.e. GCC 13.1.0 (with POSIX threads) + LLVM/Clang/LLD/LLDB 16.0.5 + MinGW-w64...

Hi @Colengms, I collected `C/C++: Log Diagnostics`: ``` -------- Diagnostics - 7/31/2024, 8:23:55 PM Version: 1.21.3 Current Configuration: { "name": "Win32", "includePath": [ "s:/Code/CPP/cpptools_repro/**" ], "defines": [ "_DEBUG", "UNICODE", "_UNICODE"...

Hi @Colengms thank you for quick response and detailed explanation, yet I still don't understand why my current configuration chooses `cl.exe` (I suppose it's MSVC compiler from Visual Studio 2022)...

Accidentally I pasted only a part of the `clang-tidy` command from `C/C++` output (I updated my previous comment to include `-isystem` flags), but include paths are the same whether I...

Unfortunately `1.7.30-25-beta` release does not fix this for me, I checked in both sandbox vault and my actual vault. But it works when creating folder note from context menu.

Can confirm that the bug is fixed in 1.7.30-26-beta, thank you!