Project

autocolors

0.0
No commit activity in last 3 years
No release in over 3 years
Inspired by solarized, and lots of work with various colorschemes and syntax highlight files, and driven by a need to have some color variety that doesn't stink. Tries to generate colorschemes with just the right contrast, variety, and coherence.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
 Dependencies

Development

~> 1.0.0
~> 1.6.4
>= 0
~> 1.2.8
~> 2.1.0
~> 0.6.0

Runtime

 Project Readme

AutoColors

Automatically create well-balanced colorschemes

Current status

Automatically generating vim colorschemes - or at least gvim gui colorschemes. Mappings are mostly done for textmate, pygments, and emacs, but no output for those yet. 256 and especially 16-color palette versions are very broken at the moment, but shouldn't be too hard to fix...

STILL EXPERIMENTAL AND CHANGING RAPIDLY. Feel free to contact me w/ suggestions & questions.

Usage

$ autocolors [COLORSCHEME_NAME]

Generates a name for you if left blank - saves it to colorscheme_name.vim in your cwd. I know, not very flexible. If you're really curious about how beautiful these are though, you can do this:

$ cd ~/.vim/colors
$ autocolors
$ autocolors
$ autocolors
... muahahaha ...

Important: These syntax files honor the background variable! So if in your .vimrc file (or whatever) you do "set background=light" or dark, you'll get the light or dark version of the colorscheme.

Quick notes

  • Palettes for ( mono / 16 / 256 / ffffff )

  • Outputs for

    • terminal emulators
    • terminal programs (email readers etc.)
    • editors
      • vim
      • emacs
      • textmate
    • syntax highlighters
      • pygments
      • perldoc (many, many more to come)
  • Possibly customized per language (different densities)

  • Properly balanced for transitions across semantics/syntax/focuses

  • Really good looking

  • Random. muahaha

Contributing to autocolors

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
  • Fork the project
  • Start a feature/bugfix branch
  • Commit and push until you are happy with your contribution
  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright / License

Copyright (c) 2011 Joseph Wecker. See LICENSE.txt for further details. (MIT License)