Zugg Software :: View topic

Newbie Joined: 09 Jan 2005 Posts: 5

I have an MXP trigger where i want to use the %0 value. Issue I have is that the %0 value seems to get cut off whenever there's a change in
ansi status. If the line i capture starts with a colored word of phrase, the %0 value gets cut off as soon as the color changes or the color stops and
if the line i capture doesn't start with ansi the value will get cut off as soon as there is some ansi.
Had the same trigger in zmud and worked there. I also tried to disable ansi while using cmud and then i get all i want in the %0 value.
Wonder if there's some way to get this to work without disabling ansi in the mud?

Basically the mud sends <mxptag attr=attr>Some text: and then some more text</mxptag>
or <mxptag attr=attr>Some text and some more text</mxptag>

Now if i have an mxptrigger that does #sa %0 it'll return 'some text' in the first case and 'Some text' in the other. So in the first case the value
will be cut off as soon as the red ends, and in the second case it will cut off as soon as the red starts. I of course want %0 to return everything within
the tag.

Appreciate any help.

Apprentice Joined: 24 Jul 2005 Posts: 137

Have you tried checking "ANSI trigger"?

Beginner Joined: 16 Oct 2011 Posts: 13

I ran into problems with ansi codes in string lists. Have you tried %stripansi() ?