|
Guess I was a bit confused by your statement. Yeah, you should have some ability to configure. There are times though where it shouldn't be, but they are rare. In any case, the limitations of ANSI means that in most cases you will never get a decent set of options anyway. Color is not much more than a way to nicely seperate stuff out, in which case you have a limited number of options to do that anyway.
In any case, the point of all this started with why muds can't figure out something that is built into the ANSI protocal and has been used everyplace, except in muds, for the last 25 years or more. If you choose to turn them off or change them doesn't matter as much as either assuming that someone "doesn't" have color by default, or tht they 'always' have it. Both are wrong and a simple solution exists to figure it out, and you don't need to know what the specific name of the client is. ANSI itself has the means to find out built in.
However, between the two wrong choices, the one that makes you hunt through help files to turn on the color, instead of having it on to start, is more wrong than the other imho.
|