Syntax highlighting for Sauerbraten's scripting langauge, Cubescript, in Sublime Text 2 & 3.
With Package Control:
- Run
Package Control: Install Package
command, find and installCubescript Syntax Highlighting
plugin. - Restart Sublime Text editor (if required)
Using Package Control ensures package will stay up to date automatically.
Manually:
-
Clone or download git repo into your Packages folder (in Sublime Text, find
Browse Packages...
menu item to open this folder) -
Restart Sublime Text editor (if required)
Example commands:
cd ~/Library/Application\ Support/Sublime\ Text\ 2/Packages git clone https://github.com/srbs/cubescript-syntax-sublime.git Cubescript
Menu:
- Open up the Syntax Menu (
View
->Syntax
) - Click
Cubescipt
Command:
- Run
Set Syntax: Cubescript
command
All *.cfg files:
- Open any *.cfg file
- Open up the Syntax Menu (
View
->Syntax
) - Select
Open all with current extension as...
- Click
Cubescript
Development for this project is primarily done in cubescript-syntax-tmbundle project. My converter is used to convert between the two structures using this build.xml
in the parent folder of all three projects:
<project basedir=".">
<include file="textmate-to-sublime-converter/tm2subl.xml" />
<tm2subl destdir="cubescript-syntax-sublime" srcdir="cubescript-syntax-tmbundle" />
</project>
Please see the respective Contributing section for contributing information.
This project uses the Zlib license. See the License section for details.
Copyright (c) 2012-2012 David "srbs" Forrest
This software is provided 'as-is', without any express or implied
warranty. In no event will the authors be held liable for any damages
arising from the use of this software.
Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not
claim that you wrote the original software. If you use this software
in a product, an acknowledgment in the product documentation would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source
distribution.