Plugin causing many other file types to open as SCSS files

[smlombardi]

I noticed all tmTheme, tmPreference, plist, sublime-settings, sublime-snippets -- and many other files that I expected and set to open as XML keep opening as SCSS files.

Even if I choose "always open as XML", they recopen as SCSS and have of course the wrong syntax coloring.

I checked the SCSS.sublime-settings file, and always find this: "hidden_extensions": ["sublime-snippet", "tmLanguage", "tmTheme", "tmSnippet", "tmPreferences"]

But even removing this line has no effect. I have confirmed it is this extension, since if I uninstall it the problem goes away.

[stephenway]

Hey @smlombardi are you using any plugins to automatically detect syntax? For instance I use the DetectSyntax package. Also have you checked to see if the XML package is enabled?

[smlombardi]

I do not have a Detect Syntax plugin. The only plugin i have set to ignore is Vintage. XML seems to be live, and xml settings file includes extensions like the ones i mentioned.

The other plugins I have: Actionscript, Alignment, BracketHighlighter, Coffeescript, Colorpicker, CSScomb, Emmet, Flex, HyperlinkHelper, JQuery, Sass Build, ScopeHunter, Sidebar Enhancements, SVN, SFTP, Tag, and Wordpress

On Thu, Jan 24, 2013 at 11:34 AM, Stephen Way notifications@github.comwrote:

Hey @smlombardi https://github.com/smlombardi are you use any plugins to automatically detect syntax? For instance I use the DetectSyntax package. Also have you checked to see if the XML package is enabled?

— Reply to this email directly or view it on GitHubhttps://github.com/kuroir/SCSS.tmbundle/issues/131#issuecomment-12659753.

[stephenway]

Hmm without the Detect Syntax plugin activated I still seem to be able to open xml files with correct syntax highlighting. I'm on latest OS X and Sublime. Can you try disabling all your user packages? Then try opening an xml file. If that works then activate the latest version of the SCSS package. Then see if an xml file works.

[smlombardi]

I deleted the SCSS package and re-installed, restarted sublime. Cleared out all user preferences for it and other languages from user folder. Seems to work again, so far.

On Thu, Jan 24, 2013 at 3:31 PM, Stephen Way notifications@github.comwrote:

Hmm without the Detect Syntax plugin activated I still seem to be able to open xml files with correct syntax highlighting. I'm on latest OS X and Sublime. Can you try disabling all your user packages? Then try opening an xml file. If that works then activate the latest version of the SCSS package. Then see if an xml file works.

— Reply to this email directly or view it on GitHubhttps://github.com/kuroir/SCSS.tmbundle/issues/131#issuecomment-12671685.

[colinta]

FWIW, I was battling this same problem this morning. .sublime-snippet files kept being opened as SCSS files, no matter how many times I ran View > Syntax > Open all with current extension as > XML.

Removing the hidden_extensions setting DID fix this for me, so for now I'm leaving it at that.

[colinta]

More info: even stranger, if I don't remove the setting altogether, and just remove the sublime-snippet from the hidden_extensions list, the problem remains! It is only "solved" when I remove the hidden_extensions setting altogether. (O_O)

[smlombardi]

I did the same fix, remove hidden_extensions, but they come back.