Bug #882
smuxi color parser incorrect
| Status: | Closed | Start: | 09/19/2013 | |
| Priority: | Low | Due date: | ||
| Assigned to: |  Mirco Bauer |
% Done: | 100% |
|
| Category: | Engine IRC | |||
| Target version: | 0.10 | |||
| Complexity: | Medium |
Found in Version: | 0.9.0.0 |
|
| Votes: | 0 |
Description
2013-09-19 15:33:33,482 [IrcProtocolManager (irc.freenode.net:6667) listener] DEBUG MESSAGEPARSER - IrcMessageData nick: 'Not-002' ident: '~notifico' host: '198.199.82.216' type: 'ChannelMessage' from: '[email protected]' channel: '#mcdevs' message: '^C[^C02netherrack^C] ^C07thinkofdeath^C ^C03b2d9b95^C - world: Limit the rate that chunks can be send/saved. Doing to many in parallel was causing the memory usage to increase by large amounts. Old memory usage 150-300MB, now 35MB' 2013-09-19 15:33:35,467 [ReadThread (irc.freenode.net:6667)] DEBUG SOCKET - received: ":[email protected] PRIVMSG #mcdevs :^C[^C02netherrack^C] ^C07thinkofdeath^C ^C0366e35a3^C - protocol: Update to 1.6.3" 2013-09-19 15:33:35,467 [IrcProtocolManager (irc.freenode.net:6667) listener] DEBUG QUEUE - read: ":[email protected] PRIVMSG #mcdevs :^C[^C02netherrack^C] ^C07thinkofdeath^C ^C0366e35a3^C - protocol: Update to 1.6.3" 2013-09-19 15:33:35,467 [IrcProtocolManager (irc.freenode.net:6667) listener] DEBUG MESSAGEPARSER - IrcMessageData nick: 'Not-002' ident: '~notifico' host: '198.199.82.216' type: 'ChannelMessage' from: '[email protected]' channel: '#mcdevs' message: '^C[^C02netherrack^C] ^C07thinkofdeath^C ^C0366e35a3^C - protocol: Update to 1.6.3'
smuxi: http://i.imgur.com/k3vPT9y.png
mirc: http://i.imgur.com/P7xb4IW.png
Yes, colors and formatting are enabled in Smuxi. Its strange, its only this plugin: http://n.tkte.ch/ that messes with the colors. Other IRC github coloring programs have no problem.
Associated revisions
Revision aa2a17caaa172ea10db65834e4b5b82b91d97084
[Engine-IRC] Fixed parsing color reset control chars properly (closes: #882)
The color code regex matched message chunks with a color reset control char
(^C) while it should not. This ate all characters between ^C and ^C[0-9].
History
Updated by Anonymous 4112 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset aa2a17caaa172ea10db65834e4b5b82b91d97084.