Neon Color Scheme
- Total 43K
- Win 23K
- Mac 11K
- Linux 9K
|Apr 19||Apr 18||Apr 17||Apr 16||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|
Neon Color Scheme
Just for clarity's sake: Neon is an original work and wasn't based on any other color scheme. If you search Package Control for
neon you'll find some other, similarly-named color schemes which are not based on this project. Use them if you want – I particularly like the Dark Neon Color Scheme, and might borrow some of the colors – and if you want to fork this project and make your own derivative, go for it! I use the MIT License for a reason.
Neon's main goal is to make as many languages as possible look as good as possible. That being said, there are some language/markup/framework-specific scopes and sections that you might be interested in:
- Android Debug Bridge/logcat
- C/C++/C Improved
- CSS/SASS/SCSS - specifically, the
Syntax Highlighting for SASSpackage
Find In Files
- Git Gutter
- PHP/Laravel Blade
- Regular Expressions
- Shell Scripts/ShellScriptImproved
- Table of Contents/Task Tags
For major changes, I'll test most if not all of the above languages, as well as Makefile, Lua, and Perl, with maybe some others thrown in for fun. When I say “as many languages as possible” I mean it!
If you have a particular language or plugin you'd like Neon to support, just open an issue and I'll see what I can do.
There are a bunch of scopes in here that are only found in my
Python Improved language definition package — IPython
Out statements, Django-specific highlighting (adapted from
Djaneiro), a bunch of improvements from @facelessuser's
Better Python and @petervaro's Python 3 package, along with various enhancements, extensions, and bug fixes of my own and contributed by others. If you work with Python, I'd highly recommend getting it.
You can find out more about themes in the TextMate manual. All the information there applies to Sublime Text as well, which was heavily influenced by TextMate. Both programs can share themes and language definitions pretty much interchangeably, and snippets are usually pretty easy to port from one to the other as well. But, unfortunately for you Win/Lin people, TextMate is only available for macOS.
What Font is That?
Cousine while browsing Google Fonts one day and absolutely love it.
Cousine was designed by Steve Matteson as an innovative, refreshing sans serif design that is metrically compatible with Courier New™. Cousine offers improved on-screen readability characteristics and the pan-European WGL character set and solves the needs of developers looking for width-compatible fonts to address document portability across platforms.
It's one of the first things I install when setting up a new workstation or VM, and it used to be my go-to monospace font for web design and programming.
More recently, I've been using
Liberation Mono, part of the Liberation font family. It's almost an exact duplicate of Cousine (with a few minor differences), and has the advantage of being available for Fedora (out of the box) and RHEL/CentOS as
liberation-fonts, and as
ttf-liberation for Debian and Ubuntu (my current distro of choice).
Installation for Sublime Text 3
The easiest method is through Package Control, which you need to install first as it doesn't come with Sublime Text. (Note: It does now!) Open the Command Palette with CtrlShiftP (Windows/Linux) or ⌘ShiftP (macOS) and type ***
pci*** to bring up
Package Control: Install. Click or hit Enter, type in
Neon Color Scheme should show up. Select it, then activate the theme by choosing the
Preferences -> Color Scheme -> Neon Color Scheme -> Neon menu option. Alternatively, paste the following line in
Preferences -> Settings - User):
"color_scheme": "Packages/Neon Color Scheme/Neon.sublime-color-scheme"
If you were using the old pre-3.0 version of Neon, the file name was
Neon.tmTheme. If you are using Neon when you upgrade, a small plugin comes with the new version that will automagically change the file name to
Neon.sublime-color-scheme. I switched formats both because JSON is far easier to work with than XML, and there are some cool new features coming in the next release of Sublime Text that don't work with
.tmTheme files. Stay tuned!
For right now, manual cloning is the only option.
Maybe I'll make a bundle someday for TM1 and TM2. From your home directory (or anywhere, really), enter:
git clone https://github.com/MattDMo/Neon-color-scheme.git "~/Library/Application Support/TextMate/Themes"
Or, you can just download the
.zip file and put it in the proper theme directory yourself. TextMate only supports the
.tmTheme format, so you won't get any new updates. Use Sublime instead!
Sometimes the same file looks different in TextMate and Sublime Text. It may be that the scopes are defined somewhat differently, or that the parsers don't work in quite the same way. Hack the
.tmlanguage definition files if you're interested, it's an exciting combination of XML and regex! To ease the pain somewhat, I definitely recommend installing
PackageDev via Package Control. Among many other things, it allows you to convert XML/Plist-based
.tmLanguage files to YAML syntax, which Neon conveniently supports! Everything is much more straightforward to understand and edit, and when you're done you can run a build system from the Command Palette to convert the YAML back to XML.
If you have questions, concerns, or suggested improvements, I'd love to hear from you! Feel free to open an issue or send a pull request and I'll get back to you as soon as I can. You can also ping me on the Twitters @MattDMo, or catch me on the Sublime Discord server.
© 2013-2021 Matt Morrison firstname.lastname@example.org.
This is free software. It is licensed under the MIT License. Feel free to use this in your own work. However, if you modify and/or redistribute it, please attribute me in some way, and it would be great if you distribute your work under this or a similar license, but it's not required. A shout-out or a beer would be appreciated.