Ever thought handwriting .tmTheme
files sucks? But the other options for
editing color schemes are not programmatical enough? Then this is for you!
CSScheme is a custom CSS-like syntax that converts into the .tmTheme
files we
all love, but it does not end there. CSScheme (the package) can also take care
of compiling SCSS, SASS or stylus into CSScheme (the syntax) and then into
a color scheme using all features of these pre-compilers, such as variables,
conditionals or functions.
Check the example files for what's possible!
Use Package Control to install "CSScheme".
You can either create a new file with the CSScheme: Create new *Scheme file
commands, open a file with the .csscheme
, .scsscheme
, .sasscheme
or
.styluscheme
extension or convert an existing tmTheme
file using the
CSScheme: Convert to CSScheme command or build system. Conversion to other
syntaxes is not supported at the moment and likely won't in the future. Please
convert manually and to your own preferences.
Building (ctrl+b or ⌘b) will convert the file to CSScheme,
if necessary, and then into a .tmTheme
file. Errors during conversion are
captured in an output panel. For automation purposes, the command is named
convert_csscheme
.
Things you must consider when using CSScheme:
@
at-rules will be added as string values to the "outer dictionary". You
may specify a global @name
rule to specify the scheme's name. @name
rules in a ruleset will show as the name for various color scheme editing
tools after compilation. Sublime Text itself does not use it..hidden-tmTheme
file, you need to specify a global
@hidden true;
rule. The converter will consume this rule and change the
output file's extension accordingly.fontStyle: none;
. This will be translated to
<key>fontStyle</key><string />
.*
selector. This is required.@uuid
) is optional because Sublime Text ignores it.Things you must consider additionally when using CSScheme with SCSS or SASS:
sass
is available on your PATH or adjust the path to the
executable in the settings.#RRGGBBAA
hashes. You must enclose
them in a string, e.g. '#12345678'
, or just use the rgba()
notation.The SASS parser will also not work with several scope selector operators (-
,
&
, (
, )
, |
). You must escape these with a backslash.
The same applies to scope-segments starting with a number.
CSScheme will take care of removing backslashes before emitting the final conversion result. Examples can be found in the example files).
Note: Because the SASS parser does not know about the semantics of these operators, they will generally behave poorly when used in conjunction with scope nesting.
Things you must consider additionally when using CSScheme with stylus:
stylus
is available on your PATH or adjust the path to the
executable in the settings.@name
must be encapsulated with
unquote()
. Example: unquote('@name "Example StyluScheme";')
@name
or possibly @comment
anyway, but stylus does some weird stuff that
does not translate into sane CSScheme.CSScheme (the package) provides native support for CSScheme-to-.tmTheme
conversion. Thus, all languages that compile to CSS will also work in one way or
another. SCSS/SASS and stylus are automatically built from within Sublime Text,
and SCSScheme even has its own syntax definition because the one from the SCSS
package highlights unknown properties as invalid. Furthermore they provide
snippets and completions.
If you want to use something a different pre-processor, you can do so by converting to CSScheme externally and then do conversion from CSScheme to tmTheme from within Sublime Text. Feel free to file an issue (if there isn't one already) if you'd like built-in support for an additional pre-processor.
(only CSScheme and SCSScheme)
Just press ctrl+r (⌘r).
In StyluScheme this is somewhat supported but since scope names are not regular html tags they don't get recognized (since I didn't bother to write a new syntax definition for stylus as well).
*
(*
ruleset)r
(general purpose ruleset)only SCSScheme:
mixin
, =
(short for mixin
)if
, elif
, else
for
(from ... to), fort
(from ... through)each
while
All known properties are completed as well as the basic scopes from the Text Mate scope naming conventions when specifying a selector.
Here is a bunch of links that might help you when working on your color scheme.
I prepared two example files that are merely a proof of concept and show a few of the features that are supported. The colors itself don't make much sense and are not good on the eyes because I picked them pretty much randomly, but it gives some great insight on what is possible.
If you would like to see a real world example, refer to the Writerly Scheme
by @alehandrof which heavily uses SASS's @import
to make a larger scheme
more manageable.
Please note that all these work directly on .tmTheme
files.