When someone writes
```
#include "<some_file.h>"
```
or
```
#include " some_file.h "
```
the compiler returns "file not fond..." with fonts and quotes that may make it hard to see there are excess quotes or surprising bytes in the filename. This feature raises a warning about likely typo and prompts for expected include statement format when:
a). the code fails to compile and errors on "file not found", and
b). the first or last character of the filename detected is a non-alphanumeric character.
Assuming that files are usually logically named and start and end with an alphanumeric character, this feature should help shorten the time for future debugging due to simple typos.