Cool, thank you very much!

I've tried to use a fairly sensible palette to keep similar things in
similar color spectrums. Text is green, code is blue, markup is blue
green, etc. That said, I'm not an artist or a color person, so happy to
have suggestions on better arrangements here.

Me neither, but it looks great 😄.

Here is a short comparison with "molokai" on my test folder:

A few things I noticed:

• The blue_grey color of category programming.tooling (see test.cmake) doesn't look very similar to the blue of programming.tooling.continuous-integration (see .travis.yml).
• fifos and sockets are not highlighted with a background color like in the other themes.
• README and TODO files are not highlighted in any special way.

All of these decisions are completely fine with me, I just wanted to point it out. Variability in the color themes is a good thing, after all.

Thanks for the feedback!

I pushed an updated version. This has a cleaned up and expanded palette section and tries to address some of the shortcomings you noticed.

Specifically, the tooling vs. continuous integration difference should be a bit less odd, and the README and TODO files are highlighted a bit better, along with some other improvements.

I've continued to avoid using a background color for fifo and socket as I prefer that to only be used on something that is broken like a symlink.

What do you think?

I pushed an updated version. This has a cleaned up and expanded palette section and tries to address some of the shortcomings you noticed.

Specifically, the tooling vs. continuous integration difference should be a bit less odd, and the README and TODO files are highlighted a bit better, along with some other improvements.

Thank you!

I've continued to avoid using a background color for fifo and socket as I prefer that to only be used on something that is broken like a symlink.

What do you think?

Sounds good to me. As I said, it's probably good to have some variability in the color themes.