XTermThemer is a tiny XTerm theme manager. It provides the dark and the bright version of the [Solarized]((http://ethanschoonover.com/solarized) color theme for XTerm out of the box, though it is capable of providing any number of themes. It allows multiple XTerm color themes to be run in one X session and decouples styling in a non-destructive way using XTerm's -name feature to extend the default XTerm X resources class (or any other class that has been defined using XTerm's -class command line parameter).

Prerequesit: XTerm with color support compiled into it (color256 or color16). (It may also be useful to export the TERM enviroment variable to tell other applications that the terminal supports colors (system-depend).)

1. Clone the repo
2. Edit pathes and options in config.py
3. ./install.py install

XTermThemer gives you everything that Solarized has to offer...

... without any hassle™.

It automagically appends the required configuration lines to the user's .Xresources and adds the provided .Xresources.<themeName> style sheets to wherever they should go to (default ~/.styleSheets/xtermStyleSheets/). To ensure a minimal signature in the user's configuration files .Xresources only includes one include file (.Xresources.styleSheetsList) which then includes all style sheets. XTermThemer also generates an alias for each style sheet and appends it to the user's shell configuration file.

Options:

• ./install.py generate: Generate template files
• ./install.py install: Install themes (writes to the user's .Xresources/shell config file etc.)
• ./install.py clear: Clear template files

Files:

• config.py: Configurations to apply when running ./install.py install
• templates/.Xresources.mixin.template: Not style sheet-related resource definitions
• templates/.Xresources.styleSheetsListHeader.template: Header for the include file
• aliases/shellFileHeader.template: Heading for the shell configuration file

During installations old configuration file settings are not altered. So it is recommended to manually remove old include statements/themes when before reinstalling, though this is not required and will not affect the new installation in any way.

Individual style sheet names should match the X resource name prefix used in them. The X resource name itself should be lowercase to differenciate them from X classes.

Example - .Xresources.solarizedDarkXTerm.template uses the prefix name solarizedDarkXTerm:

! ...
solarizedDarkXTerm*background:              S_base03
solarizedDarkXTerm*foreground:              S_base0
solarizedDarkXTerm*fading:                  40
solarizedDarkXTerm*fadeColor:               S_base03
solarizedDarkXTerm*cursorColor:             S_base1
! ...

It is recommended to use the .Xresources. prefix to clarify that themes are essentially just .Xresources includes and to use the Suffix prefix to avoid confusion with future resources setup.

All style sheets templates should have a leading . since they are valid X resource files (and could pententially be merged individually using xrdb -merge .<themeName>).

The pathes in the resources files are generated in a context-agnostic way. So they are full pathes.

• Python 2.7.2+
• Linux

Have a look at:

• styleSheets/.Xresources.solarizedBrightXTerm
• styleSheets/.Xresources.solarizedDarkXTerm

Feel free to add themes!