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 Sep 3, 2021. It is now read-only.
I'm aware that tmLanguage file is essentially an XML file, and that json-tmLanguage and yaml-tmLanguage file is a JSON, and YAML file respectively. But this is not vice versa; not all XML, YAML, and or JSON file is a *tmLanguage file.
I think the extension should not be activated for an XML, YAML, or JSON file by default.
If user does need to have an XML, YAML, or JSON file treated as tmLanguage file, he/she can still do so via the Change Language Mode dropdown.
The text was updated successfully, but these errors were encountered:
The extension manifest (
package.json
) defines theactivationEvents
as:I'm aware that
tmLanguage
file is essentially anXML
file, and thatjson-tmLanguage
andyaml-tmLanguage
file is aJSON
, andYAML
file respectively. But this is not vice versa; not allXML
,YAML
, and orJSON
file is a*tmLanguage
file.I think the extension should not be activated for an
XML
,YAML
, orJSON
file by default.If user does need to have an
XML
,YAML
, orJSON
file treated astmLanguage
file, he/she can still do so via theChange Language Mode
dropdown.The text was updated successfully, but these errors were encountered: