el-get/recipes/color-theme-tangotango.rcp

(:name color-theme-tangotango
       :description "Another color theme based on the Tango palette."
       :type github
       :pkgname "juba/color-theme-tangotango"
       :depends color-theme
       :post-init (autoload 'color-theme-tangotango "color-theme-tangotango"
                    "color-theme: tangotango" t))
Add recipe for color-theme-tangotango 2011-09-20 21:12:50 +08:00			`(:name color-theme-tangotango`
			`:description "Another color theme based on the Tango palette."`
Convert all github recipes to github type This automated convertsion was done with the following sequence of commands: cd recipes # Replace :url with :pkgname "user/repo" perl -iBAK -lape 's{^(\s):url\s+".github.com/([^/]+)/([^.]+)\.git"}{$1:pkgname "$2/$3"}' .rcp # Change :type from git to github if recipe has a :pkgname property for x in .rcp; do if grep -q ":type.git" $x && grep -q ":pkgname" $x; then perl -iBAK2 -lape 's/:type\s+git\b/:type github/g' $x; fi; done # Clean up backup files rm -f BAK *BAK2 cd .. These commands may be repeated at any time in the future to convert newly-added recipes. 2012-02-21 06:43:23 +08:00			`:type github`
			`:pkgname "juba/color-theme-tangotango"`
color themes depend on color-theme and are automatically required Autoloads are rarely (if ever?) present for color themes. color-theme-zenburn installs its own in the :post-init hook, but that's not typically done for el-get packages, so I've just added a :load or :feature property (depending on whether the library provides a feature). For color-theme-twilight, the current version available automatically installs itself as the current color theme, so the :feature property is omitted. I have a pull request in to the project, so if that's fixed, I'll add it. 2011-10-15 02:59:23 +08:00			`:depends color-theme`
Eliminate lambdas from :post-init in recipes 2012-02-23 05:43:32 +08:00			`:post-init (autoload 'color-theme-tangotango "color-theme-tangotango"`
			`"color-theme: tangotango" t))`