Page 1 of 1
CMUD: Syntax trigger on HTML ... failed to compile.
Posted: 17 Mar 2013 15:22
by Mercade
Seems that somehow my CMUD (3.34) doesn't like to fire its own default triggers for syntax colouring on url's and e-mail addresses.
Any ideas what may be causing this, or how to get rid of it (other than disabling triggers) is appreciated.
You say: http://www.foobar.com
ERROR: Trigger "\b(((https?|ftp|telnet)://[\w\d:#@%/;$()~_?\+\-=&]+|www|ftp)(\.[\w\d:#@%/;$()~_?\+\-=&]+)+)\b" fired but did not compile
You say: foo@bar.com
ERROR: Trigger "\b([\w\d._%+\-]+@[\w\d.\-]+\.[\w]{2,4})\b" fired but did not compile
Re: CMUD: Syntax trigger on HTML ... failed to compile.
Posted: 17 Mar 2013 19:52
by Zhar
E-mail: [A-Za-z0-9 _-]*[.|_|-](.*)@(.*)\.[A-Za-z]*
Links: (https|http|ftp|telnet)\:\/\/(.*)\.[A-Za-z]*
Seems to be working just fine. Not CMud but regular expressions should be pretty adaptable

Re: CMUD: Syntax trigger on HTML ... failed to compile.
Posted: 17 Mar 2013 23:39
by Mercade
My issue isn't so much that I'm trying to debug the trigger. These are apparently part of the CMud out-of-the-box triggers to make syntax colouring, but somehow it's unhappy.
Re: CMUD: Syntax trigger on HTML ... failed to compile.
Posted: 17 Mar 2013 23:48
by Zhar
Well, there are a lot of statements in there. I'm not really sure what some of them do, like the "%/" for example. As I read up on it, it denotes a regex match inbetween the %/ and /%, which would indicate that there's a missing closing case for this - depending on how Cmud treats non-closed statements, if it works like old html where you could leave out the closing tags then I'm no more wiser.
Re: CMUD: Syntax trigger on HTML ... failed to compile.
Posted: 18 Mar 2013 00:16
by Mercade
Again, I'm not after debugging that trigger statement. I didn't write it; in fact, I don't know where it's contained within CMud (something I'd like to find out, though).
Re: CMUD: Syntax trigger on HTML ... failed to compile.
Posted: 18 Mar 2013 00:51
by Zhar
Sorry then, the only other helpful thing I found is that you get such error in cmud when 2 different triggers are trying to fire on the same string.
From their forums:
Apparently, I had 2 separate triggers set for the same text string, and that was causing the problem.
The first one had the color highlight action and the second one had the #speak command - which was causing the problem.
As soon as I deleted it, the error disappeared.