Zugg Software :: View topic - [3.17]Bug: %e[37m no longer being interpreted correctly

Posted: Sat May 08, 2010 5:10 pm

Tested in 3.16b, it works. Tested in 3.17, it doesn't. This actually breaks a couple of my ansi scripts, including my note email system.

Easy way to check this is to do this:
1. Open untitled session.
2. On command line, type #SHOW {%e[37mTesting}
3. Copy that line.
4. Open up Settings Editor.
5. Create New Trigger, tick 'Ansi Trigger'
6. Paste highlighted text. Instead of showing %e[37mTesting like it should, it just shows Testing.
7. To ensure that Ansi triggers are working properly, do #SHOW {%e[32mTesting} on command line and repeat steps 5 and 6. You'll see it correctly puts %e[32mTesting in the pattern field.

This also breaks color syntax for just that color. Not sure what the problem is, but I wouldn't be surprised if it had something to do with the change in ansi code you made with this release.

Charneus

Posted: Sat May 08, 2010 5:45 pm

That's probably because your default output color is set to the %e[37m color (silver). So when you copy/paste the line, it drops the color code because it's already the same color as the default.

Unfortunately, this is related to the issue with fixing the #SAY command (the color of the first letter was wrong). I forget if that was your own bug report or one of ReedNs (or somebody elses).

If you really need this to work for some reason, you can try just changing your default text color so that it doesn't exact match the same color as the ANSI gray value. That will trick CMUD into thinking that the %e[37m line isn't the same as the default text style.

Posted: Sat May 08, 2010 5:54 pm

Good call on that one... that's exactly what it was. And I figured it was due to the change with the ansi code you made (regarding #SAY). Just surprised me that it worked in 3.16 and not 3.17. Thanks for the fix/workaround. :)

Charneus