Edit by @rsese: from Max in #308 (comment):

It sounds like you want built-in types (like int) to have a different color than user-defined types (like MyLibraryInteger in the example above). I think that makes sense, but I'd like to keep it as a subtly different color (as opposed to a completely different color), because I think there's a lot of value in coloring types consistently for visual understanding of structure.

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

any word following a preceding keyword is highlighted as a keyword, even if it is not valid

Steps to Reproduce

Consider the following code:

unsigned int y; // correct

// wrong:
unsigned integer x;
inline integer z;

Expected behavior: 'integer' is not highlighted, as it is not a valid keyword
Words following preceding keyword are only highlighted if they are also actual keywords.

Github and VS Code C highlighting does this correctly.

Actual behavior: any word following a preceding keyword is highlighted as a keyword, even if it is not valid

Reproduces how often: Always

Versions

0.60.13
atom 1.32.2