Alabaster Color Scheme
A light color scheme with minimal amount of highlighting for Sublime Text 3
- Total 3K
- Win 2K
- Mac 1K
- Linux 631
|Apr 15||Apr 14||Apr 13||Apr 12||Apr 11||Apr 10||Apr 9||Apr 8||Apr 7||Apr 6||Apr 5||Apr 4||Apr 3||Apr 2||Apr 1||Mar 31||Mar 30||Mar 29||Mar 28||Mar 27||Mar 26||Mar 25||Mar 24||Mar 23||Mar 22||Mar 21||Mar 20||Mar 19||Mar 18||Mar 17||Mar 16||Mar 15||Mar 14||Mar 13||Mar 12||Mar 11||Mar 10||Mar 9||Mar 8||Mar 7||Mar 6||Mar 5||Mar 4||Mar 3||Mar 2||Mar 1|
Alabaster Color Scheme
A light color scheme with minimal amount of highlighting for Sublime Text 3.
Most color schemes highlight everything they can, ending up looking like a fireworks show.
Instead, Alabaster uses minimal highlighting; it defines just four classes:
- All statically known constants (numbers, symbols, keywords, boolean values)
- Global definitions
Alabaster does not highlight standard language keywords (if, else, function, etc). They are usually least important and most obvious part of any program.
Alabaster highlights comments. Most schemes try to dim comments by using low-contrast greys. I think if code was complex enough that it deserved an explanation then it’s that explanation we should see and read first. It would be a crime to hide it.
Alabaster doesn’t use font variations. It’s hard to scan code when it jumps between normal, bold and italics all the time. Also, not all fonts provide bold/italics variants.
Having minimal amount of rules means you can consciously use them to look for the exact piece of information you need. Most other “fireworks” schemes provide only one meaningful contribution: if it’s colored it’s probably syntactically correct. Instead, in Alabaster you can actually remember all the rules, and e.g. if you need to look for a string you know that you’re looking for a green token. And all the strings really pop out because there are not many other things highlighted.
Alabaster only highlights things that parser could identify reliably. I believe that if highlighting works only partially then it does more harm than good. When highlighting works reliably, your brain learns to rely on it. When it’s not reliable, your brain spends precious brain cycles to re-check everything it sees on the screen.
Alabaster BG is a variation of the same scheme but it uses background color for highlighting instead of text color. The idea is that it is easier to read when all text is black rather than when it changes color every few words. The colored background in that case creates a separate layer which is easier to ignore if you just trying to read the words.
Alabaster Dark is just a dark version based on the same principles.
Alabaster Mono and Alabaster Dark Mono are monochromatic version, with only cursor and occasional errors/search results highlighted.
What our users are saying?
It's like I had this weight on my eyes, and now it's gone. Awesome!
– Alex Sugak ★★★★★
After your theme others looks like unreadable neon things 🤯
– lamartire ★★★★★
– denisgrib ★★★★★
Super minimal and undistracting. Easy to read.
– Josh Bernitt ★★★★★
A little bit confusing at first if you're from The Dark Land. But then you just chill.
– aenor.realm ★★★★★
Both schemes are packed in the same package.
Via Package Control
First, install Alabaster via Package Control:
Package Control: Install Package
Alabaster Color Schemeand press Enter.
Then, enable it:
Preferences → Color Scheme ...
Alabaster BG) for light variant and
Alabaster Darkfor dark variant.
- for Visual Studio Code tonsky/vscode-theme-alabaster
- for Vim agudulin/vim-colors-alabaster
- for JetBrains IDEs (IntelliJ IDEA etc) tonsky/intellij-alabaster
- for Sublime Text 2 (unofficial) freetonik/Travertine
- Dark for Visual Studio Code apust/vscode-rubber-theme
- for LigthTable tonsky/alabaster-lighttable-skin
- for CudaText
- for Windows Terminal awbv/Windows-Terminal-Alabaster-Scheme
Writer Color Scheme: minimal color scheme for long-term writing.
Profile Switcher: Switch quickly between writing and coding profiles.
Fira Code: Best coding font in the world.
Made by Niki Tonsky.