We where so worried about other things, including MXP, that this slipped under the radar or something. Basically, an application called xTerm supports an extension to ANSI for using 256 colors. The codes work as described here:
http://frexx.de/xterm-256-notes/
Not sure, but I think the colors can be set to anything you want, but there are pre-built sets. In other words, you would need a second "xTerm" color dialog off the one for changing ansi settings, which would bring up the palette you can edit for them all, as well as possibly load a .vim file that has an existing table layout, like those linked to in the page I gave above.
It seems the latest version of TinTin++ now incorporates this feature, as they have combined the code for Putty and TinTin++ into one, and one of them has support for it. This appears to be something that lacks negotiation though. I.e., the client will either support it or not, but the server has no way to tell "if" that feature is supported through the negotiation sequences.
Note: This could probably be handled with the packet intercept and replacement (through simulate) trick, but we should imho limit that, since if everyone "fixes" problems that way, then you start running into "whose" intercept needs to work on the line first, to make sure everything happens as its supposed to, much like problems people are having with more than one plugin using the same line already.
Also, we might want to keep an eye on this:
http://firebolt.com/IMP-rfc.php
They seem to be reinventing MXP there. So far, most of it, except the ones like clearing the text display, which Mushclient can't even do using ANSI codes anyway, appear to be fairly similar to MXP's functions. That might change as they expand the feature set though.
http://frexx.de/xterm-256-notes/
Not sure, but I think the colors can be set to anything you want, but there are pre-built sets. In other words, you would need a second "xTerm" color dialog off the one for changing ansi settings, which would bring up the palette you can edit for them all, as well as possibly load a .vim file that has an existing table layout, like those linked to in the page I gave above.
It seems the latest version of TinTin++ now incorporates this feature, as they have combined the code for Putty and TinTin++ into one, and one of them has support for it. This appears to be something that lacks negotiation though. I.e., the client will either support it or not, but the server has no way to tell "if" that feature is supported through the negotiation sequences.
Note: This could probably be handled with the packet intercept and replacement (through simulate) trick, but we should imho limit that, since if everyone "fixes" problems that way, then you start running into "whose" intercept needs to work on the line first, to make sure everything happens as its supposed to, much like problems people are having with more than one plugin using the same line already.
Also, we might want to keep an eye on this:
http://firebolt.com/IMP-rfc.php
They seem to be reinventing MXP there. So far, most of it, except the ones like clearing the text display, which Mushclient can't even do using ANSI codes anyway, appear to be fairly similar to MXP's functions. That might change as they expand the feature set though.





