You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is Issue 755 moved from a Google Code project.
Added by 2011-12-21T22:13:49.000Z by dmel...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Original labels: Type-Enhancement, Priority-Medium, Component-IDE
Original description
What change would like to see?
The keywords.txt file should come from the active core and variant, rather than being globally defined. (Both in addition to the per-library keywords.txt files). That way, the syntax highlighting will be correct, even for cores with differing APIs.
The text was updated successfully, but these errors were encountered:
I believe #3847 at least partially solves this issue. It provides keywords.txt at the architecture directory level, for all cores and variants within an architecture folder.
Perhaps that's good enough?
If not, at least it lays the groundwork to re-read keywords at runtime when boards change....
This is Issue 755 moved from a Google Code project.
Added by 2011-12-21T22:13:49.000Z by dmel...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Original labels: Type-Enhancement, Priority-Medium, Component-IDE
Original description
What change would like to see?
The keywords.txt file should come from the active core and variant, rather than being globally defined. (Both in addition to the per-library keywords.txt files). That way, the syntax highlighting will be correct, even for cores with differing APIs.
The text was updated successfully, but these errors were encountered: