 |
john_taylor_jr
Wanderer
Joined: 17 Jan 2003
Posts: 57
Location: USA
|
 Posted: Tue May 04, 2004 8:07 am
Anoying Ansi
|
I have a status line that isn't vt100
Toward the end of the line it represents my image spells with the
@@@@
sign
The number of @@@ left is the number of images I have left.
I have two different images
@@@@@@@ @@@@@@@@@@@
I use a trigger like
%e[35m(%x)
to capture the purple part.
reparse with
%e[0m(%x)
to capture the green part
Because either purple or green could come first.
However zmud is not triggering either of these lines.
Note both trigs are reparses of an earlier trigger. |
|
|
|
|
john_taylor_jr
Wanderer
Joined: 17 Jan 2003
Posts: 57
Location: USA
|
Posted: Tue May 04, 2004 9:52 pm
|
Ok I found what the problem is. In order to have an ansi condition the entire trigger must be ansi. This is real annoying. Any way you can make it so that conditions that require an ansi match will match for ansi independently of the main trig? Ansi is such a pain and alot of people seem confused.
|
|
|
|
|
LightBulb
MASTER
Joined: 28 Nov 2000
Posts: 4817
Location: USA
|
Posted: Thu May 06, 2004 7:28 pm
|
Since most triggers don't need the ANSI information, and it would actually only be in their way, they don't capture it. It's not possible to "reparse" information that wasn't captured originally.
I don't think there's anything to prevent other CONDITION types, which have their own patterns instead of relying on a pattern from a previous state, from using the color/ANSI option. |
|
|
|
|
|
|
|
