Some modernisation to the prompt trigger (which splits a prompt and text when CF sends them together in one line).
Now it should stop further trigger processing to avoid double firing for your lazily written triggers :). Pay additional attention to its priority. You would want all your other prompt triggers be higher priority and other trigger be lower priority than this one. I also updated the pattern itself to make it fire less often when you use CF colors.

I can't edit the xml file posted below, so you have to replace the old version manually.
Open CFbase/Prompt class and replace the prompt trigger with this one.
Just open xml tab in the source code editor and replace it with new xml definition. Then save it, open the "script text" tab and replace "ESC" with the real escape char, two instances in the pattern and one instance in the code (copy it from here: )

<table width=100% border=0 bgcolor=yellow><tr><td><tt><pre>
&lt;trigger priority="101" case="true" ansi="true" stop="true" regex="true" id="720"&gt;
&lt;pattern&gt;&lt;![CDATA[(^(ESC\[0[Sm])?&lt;.*\d+.*\d+.*\d+.*&gt; )(?!ESC\[0m$)(.+)$]]&gt;&lt;/pattern&gt;
&lt;value&gt;; Should be high priority, but lower than other prompt triggers
; because it stops further processing
#GAG
#IF (%2 = %null)
{
#PRINT "ESC[0S"%1
}
{
#PRINT {%1}
}
#SHOW %3&lt;/value&gt;
&lt;/trigger&gt;</pre></tt></td></tr></table>



Edited 12 time(s). Last edit at 09/24/2008 08:23PM by Dwoggurd.