Skip to content

Conversation

@ctf0
Copy link

@ctf0 ctf0 commented Sep 12, 2016

also changed xml scope for better&faster read of colors + support
something like

<string><![CDATA[ html { position: relative; color:#A83B40; } ]]></string>

also changed xml scope for better&faster read of colors + support
something like (<string><![CDATA[ html { position: relative; color:
#A83B40; } ]]></string>)
"syntax_files": [],
"syntax_filter": "whitelist",
"base_scopes": ["text.xml"],
"scan_scopes": ["text.xml -meta.tag.xml -comment -string"],
Copy link
Owner

@facelessuser facelessuser Sep 12, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not okay with this change. Why not do something like this?

"scan_scopes": ["text.xml -meta.tag.xml -comment -string, string.unquoted.cdata.xml"],

@ctf0
Copy link
Author

ctf0 commented Sep 12, 2016

because its not future proof, it means that with every time something new comes out u will have to update the settings.
also its faster in picking up the colors because now the plugin doesn't need to search for nested scopes.

@facelessuser
Copy link
Owner

because its not future proof

Very little in this world is.

it means that with every time something new comes out u will have to update the settings

I don't think the XML language changes very much and nor does the color schemes, and we never want to search comments. CDATA makes sense in the context of color schemes which is why I am okay with it. Comments and XML attribute strings don't.

@facelessuser
Copy link
Owner

In my defense though, a setting file that can be easily updated when changes are needed does kind of make it future proof 😉 . It's all relative to the angle you are viewing it from.

@ctf0
Copy link
Author

ctf0 commented Sep 12, 2016

okay than.

@ctf0 ctf0 closed this Sep 12, 2016
@facelessuser
Copy link
Owner

Is there a reason the issue got closed and not updated? I have no problems adding stTheme and hex_compressed.

@ctf0
Copy link
Author

ctf0 commented Sep 12, 2016

aaaaaa,okay ,my bad

@ctf0 ctf0 reopened this Sep 12, 2016
@facelessuser
Copy link
Owner

I was just reviewing the code, wasn't trying to shut this down 😉.

@ctf0
Copy link
Author

ctf0 commented Sep 12, 2016

point taken 👍

@facelessuser
Copy link
Owner

I just went ahead and manually merged what I wanted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants