Peter S. Hollander

> The warning is produced by a new feature in clangd 17 called [include cleaner](https://clangd.llvm.org/guides/include-cleaner). I am new to using clangd, but is there a way that it could more...

Thank you @HighCommander4 - I just updated my `.clangd` to feature: ``` Diagnostics: MissingIncludes: Strict UnusedIncludes: None ``` I now see the informational suggestions, and they do not increase my...

I would like to voice support for reparsing opened files upon `compile_commands.json` change! A number of times as I have been setting up my build environment, I keep thinking I've...

> 1. Technically, `--query-driver` is not _just_ a security mechanism for the user to confirm that drivers on this list are safe to execute, it's also a functional mechanism for...

Checking in to say that GCC `@/path/to/file` response files work again in clangd 18.1.3, but *only* from within `compile_commands.json`. I am unable to get response files to work (at least...

I definitely agree that the order of operations to apply `CompileFlags:` after `compile_commands.json` makes sense, but is there any reason not to also parse response files found in `CompileFlags:` once...

Cool 🙂 Would you like me to open a separate feature request for that, or is this thread sufficient?

> I've never had the time to dig through all of the licensing to figure out which one I like. @pico-coder Thanks for all your work on this project! I'm...

Hi Richard, My previous message was actually intended for @pico-coder (the owner of the sigrok-pico repository) regarding licensing the firmware they've written here. I was piggy-backing on this thread you...