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
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
I had to leave out a few details to make the summary short, but a double keyworded variable with 32 strings on one line causes the syntax highlighting to continue whatever color ended the array for the rest of the file.
It is important that the variable have two highlight regions before it; you can use a separate keyword, modifier or even a comment, so long as it has to switch highlighting contexts.
I managed to boil down a reproducible test case from the original mess into this:
cat >foo.c<<C1int main() {unsigned char *sigs[]={""$(for i in`seq 1 31`;doecho -n ',""'; done)};int i;};C1
atom foo.c
The text was updated successfully, but these errors were encountered:
I believe this is a duplicate of atom/atom#1667 where the issue is that the line is too long and colorization stops/breaks at a certain token limit (currently, 100). Please subscribe to atom/atom#1667 for updates about this.
This is with 0.15.0 which is the current version in atom.
I had to leave out a few details to make the summary short, but a double keyworded variable with 32 strings on one line causes the syntax highlighting to continue whatever color ended the array for the rest of the file.
It is important that the variable have two highlight regions before it; you can use a separate keyword, modifier or even a comment, so long as it has to switch highlighting contexts.
I managed to boil down a reproducible test case from the original mess into this:
The text was updated successfully, but these errors were encountered: