#Sublime text theme for xml files install#
#Sublime text theme for xml files code#
#Sublime text theme for xml files plus#

There are a few edge cases I still need to sort out, but for now at least, it’s very usable. In its current state, it’s about 95% complete.

The custom syntax highlighting was written for use with assembly files to be compiled by win2c64.

#Sublime text theme for xml files plus#

The theme is simply titled “Monokai Extended”, which contains all the default definitions of Monokai, plus a handful of additional definitions I’ve added to use with a custom syntax. There are two parts to the colour scheme – the theme and the syntax highlighting. Once I settled on using the win2c64 assembler, I set about creating a custom theme and syntax highlighting definition to use with it. When I began writing 6510 assembly a few weeks back, I couldn’t find much in the way of syntax highlighting for it. Plus I can use it on the Mac, Linux and Windows to maintain a consistent editing environment. I find it the most feature packed and flexible editor around.

#Sublime text theme for xml files code#

tmLanguage file to be used.Since posting screen shots of my code in previous posts, I’ve received a number of queries from people asking about what editor I’m using and what the syntax highlighting is. tmLanguage format is still supported, however, but we needed to override the XML/XML.sublime-syntax file first in order for our new. sublime-syntax format was introduced, and all of the default syntax definitions were converted. However, starting with dev build 3084 and beyond, a new YAML-based.

For ST3 builds 3083 and before, the same XML-based. However, if you create a folder and file in the Packages folder with the same name as a package ( XML in this case) and file contained within it, the version in Packages will override the version in the sublime-package archive.

#Sublime text theme for xml files install#

In Sublime Text 3, the default packages (and many that you install with Package Control) are stored in a separate directory as zipped. Here, we simply replace the old language definition (. There will be a new entry in the syntax menu called XML-ss (for sublime- syntax), just ignore it. The next time you open an XML file in Sublime, it will use the new syntax. Create a new folder in Packages named XML and copy the new XML.tmLanguage and XML.sublime-syntax files from your Desktop to Packages/XML.

Open your Packages folder by selecting Preferences → Browse Packages…, then close Sublime. Save this file to your Desktop as XML.sublime-syntax. Create another new file in Sublime with the following contents: %YAML 1.2 Save the file to your Desktop as XML.tmLanguage. In Sublime, open a new file and paste in the contents of the gist. Now, copy the new XML.tmLanguage from your Desktop to Packages/XML. Scroll down to the XML folder and rename XML.tmLanguage as. However, replacing it with the file in this gist fixes that problem, along with a few minor things: Note: The Neon Color Scheme is used for syntax highlighting The XML syntax highlighting language definition that ships with Sublime Text 2/3 does not recognize non-ASCII tags: