Agree that include path clashes is not uncommon, especially for portable software that has multiple backends, and therefore multiple versions of the same include. Can we use the path instead of just the name, presumably that is handled since Geany can open two files of the same name and symbols don't get mixed up (hopefully can't try ATM).
If you mean what I said above, I agree. But note that we can't know exactly what header at what path to use. We only see includes like ``` #include "header.h" ``` but we don't know their exact path (which may be determined by e.g. `gcc -I include_path`)