ChromaTerm v0.5.0

• Removed support for the deprecated group key in a rule; per-group coloring is still supported, just not using the group key.
• Removed uninstallation note for legacy ChromaTerm.
• A bit o' cleanup.

Upgrade with pip3 install -U chromaterm

ChromaTerm v0.4.8

• Fixed a bug when the input contains multiple combined colors (multiple SGR's into a single ANSI escape code).

Upgrade with pip3 install -U chromaterm

ChromaTerm v0.4.7

• Fixed a rare bug where the type of a color was not updated if it was a full reset in the middle of the new color.
• Optimized color handling and tracking.
• Update license classifier for PyPI.
• Removed a bit of redundant code and simplified color type internals.

Upgrade with pip3 install -U chromaterm

ChromaTerm v0.4.6

• Improved handling of existing colors in the input data; ct will now detect the type(s) of a compound ANSI code (e.g. foreground and background colors combined into a single SGR sequence).

Upgrade with pip3 install -U chromaterm

ChromaTerm v0.4.5

• Significantly improved the quality of color tracking by doing it per type (i.e. independent foreground, background, and per-style color tracking). This fixes a bug when using, for example, vi which, on some platforms, injects some color-resets at start-up to ensure deterministic output.
• Adjusted the chunk size per read to increase responsiveness when coloring lots of output.
• Improved performance by removing some redundant operations.
• Changed license to MIT. The master branch of this project is not related to the original ChromaTerm; I prefer to be more relaxed with my code and its license.
• Minor cleanup of readme.

Upgrade with pip3 install -U chromaterm

ChromaTerm 0.4.4

• Any existing colors are temporarily removed from the input before RegEx matching occurs, making the RegEx of the rules more accurate.
• Minor code cleanup.

Upgrade with pip3 install -U chromaterm

ChromaTerm v0.4.3

• No operational changes. Just a bit of cleanup on readme and the setup script.

Upgrade with pip3 install -U chromaterm

ChromaTerm v0.4.2

• #71 - Added --reload program argument to instruct all other ChromaTerm instances to reload their config.
• #72 - Support for terminal styles (e.g. bold).
• Multiple colors are compiled into a single Control Sequence Introducer (CSI).
• Added deprecation message to group key.

Once again, thanks to @Ren60FHk for the suggestions.

Upgrade with pip3 install -U chromaterm

ChromaTerm v0.4.1

• #70 - Support for multiple groups per rule. Thanks @Ren60FHk for the suggestion.
• Highlighting using a group-specific rule to an optional RegEx group which is not part of the match outputs malformed data.

Upgrade with pip3 install -U chromaterm

ChromaTerm v0.4.0

With a major rewrite into Python 3, the new code is leaps and bounds better than what it was.

• Configuration file format standardized to YAML. This will make any future changes seamless as well as backwards- and forwards-compatible. It's also nicer to read.
• Simple installation via PyPI with pip3 install chromaterm.
• The color of a rule can optionally be applied to a specific group. By default, it'll color the entire match.
• Color format changed to hex. It is automatically downscaled to the closest xterm-256 color.
• RGB support. The support in your terminal is automatically detected but can be force-enabled with --rgb.
• Simplified the rule definitions by removing the priority as it is no longer required (see next point).
• Highlight rules can now overlap (collide). Previously, there was a mechanism to prevent this as it wasn't handled very nicely. But not anymore – ChromaTerm will color text as instructed by the rules.
• The default highlight rules have been improved to cover more edge-cases, while being simpler.
• Much better handling of colors in the input. Now, the color of unhighlighted text is restored to what it was. Previously, it was always reset to the default terminal text color.
• ChromaTerm now takes into account ANSI movement sequences, reducing false-positive (mis)matching.

Huge thanks for @cpriest for his suggestions; He took the initiative of raising the issues.

When you run the new ChromaTerm for the first time, it'll create $HOME/.chromaterm.yml with the default rules. Due to the RegEx engine change, automatic migration is not possible, so you need to manually migrate any rules you created.

Now that ChromaTerm-- is more prevalent than it's predecessor, it's been given back its original name of ChromaTerm.