Open LokiChaos opened 9 years ago
Started work on this, mostly impacts channel captures as those are the vast majority of color-achored actions. Setting 256-color mode on results in exclusive use of the 256-color control codes, even for the standard colours. Actions will be converted to supporting both colour control codes.
I have a library written that algorithmically generates ANSI colour control sequence patterns, however I want to test it heavily and clean it up before it is integrated and used for triggers.
Also testing this as a client-side fix for MM's insane "reset" control code when in 256-color mode:
#sub {~\e[0\;38\;5\;7m\e[0\;40m} {\e[0m}
A quick test seems to indicate it works for rxvt-unicode and has no side affects, aside from if one specifically does want to set the FG/BG to Color7 on Color 0 (White on Black) explicitly.
That "reset" SGR sequence is a bug and will be fixed.
I have added the sgr system to vt.tt that should allow for very easy colour-aware pattern matching. Need to test it more then convert #actions to use it.
All but Archon Talk should be using the SGR lib now so 256 AND normal colour modes should be fully supported now. I do need to do a systematic test of all captures in both colour modes, but quick testing seems to show that clan/novice/ally/tells/relay/shout/yell work.
Say is currently broken, but it was before. I should probably add dream as well.
Says /might/ be fixed now. Added dream capture. Added emote capture.
Some things break with the change in the ANSI terminal control codes when 256-color is enabled. Actions that use ANSI control codes should support both the regular and 256-color variants.
While I'm at it, I should extract ANSI control codes into an array to make actions more readable.