Sublime Forum

Error loading Packages/XML/XSL.tmLanguage

#1

Hi there,

Every time I open Sublime Text build 3103 in Windows 8.1 I get that message:

Error loading syntax file “Packages/XML/XSL.tmLanguage”: Unable to open Packages/XML/XSL.tmLanguage

Is there anything I can do to get rid of it, or to fix whatever is wrong?

Cheers, Manuel

0 Likes

#2

I guess that you have a plugin installed referencing xsl language but in 3103, the syntax file were changed. You’ll need to identify which plugin does that and then fix the plugin yourself (should not be too hard) or report the issue to the plugin maintainer.

0 Likes

#3

Thanks, Clams.

Where can I find installed plugins? Are they in folder AppData/Roaming/Sublime Text 3/Packages, by any change?

0 Likes

#4

Yes, and also inside AppData\Roaming\Sublime Text 3\Installed Packages
Those inside Installed Packages or in compressed form (they decompress just like a normal zip.

Edit: Looking on the github repo, there is similar issue, it does not seem to be package related: https://github.com/SublimeTextIssues/DefaultPackages/issues/135

0 Likes

#5

There is no longer an XSL syntax as part of the default packages. However, I would imagine that the XML syntax would likely suffice. I don’t know for sure if this is true.

I think there may be two reasons why you would receive a popup about this:

  1. You have open files that previously were being highlighted with the XSL syntax. Switch to the file and change it to use the XML syntax instead.
  2. Some sort of package is trying to use the XSL syntax for a view or output panel. If you have Package Control installed, you can try using it to disable packages to see if it helps.
0 Likes

#6

Thank you for all your replies. It didn’t seem package-related. I noticed I had a couple of XSLT files open, and closing them made the warning go away.

Thanks!

0 Likes

#7

Unfortunately, using the XML syntax does not suffice. You lose all of the emmet support for xsl editing. I really really need this feature back, I use it extensively and made the mistake of recently updating my install of ST3. Does anyone have any idea of how to get this working in the current version?

0 Likes

#8

Unfortunately, this seems universally ignored by the developers. I need this too :frowning:

I used a lot of xsl specific shortcuts, like:

tn -> <xsl:template name=""></xsl:template>
for -> <xsl:for-each select=""></xsl:for-each>

There’s a whole section in Emmet for this, which is currently broken.

0 Likes

#9

This sounds more like an Emmet issue, which should include its own version of xls syntax since it is no longer part of ST3.

0 Likes

#10

I raised an issue there too.

But what emmet does depends on the filetype. There used to be an XSL filetype and Emmet did it’s XSL thing. Now there’s only XML filetype and emmet only does it’s XML thing.

0 Likes

#11

https://packagecontrol.io/packages/XSL

1 Like

#12

I added the old XSL syntax as a package that can be installed via Package Control. Hopefully this should allow you to utilize Emmet as you used to @crewone.

1 Like

#13

Epic! You made my day!

0 Likes

#14

Do you happen to know why the XSL syntax was stripped out in the first place? What did it do previously that was seemingly not needed anymore?

(the corresponding issue on github)

0 Likes

#15

No, I don’t, and Jon did not recall either.

My understanding is that XSL is just XML, correct? I would think the XML syntax should handle any XSL document. It is my guess this is why it was removed.

1 Like