Zugg Software :: View topic

Apprentice Joined: 29 Jul 2002 Posts: 105

I tried searching, but couldn't find any of the old topics. I'm stumped, I avoided conditions forever, because it always broke on me. But I figured I'll give it another shot.

#trigger {you tell} {#capture tells}
#cond { %s*} {#capture tells} {looppar|param=50}

ALTERNATIVELY
#cond { %s*} {#capture tells} {looplines|param=50}

Either way, it wants to go through 50 lines before it says okay I can capture another tell. I can get tells of 1 to infinite lines (most I had was around 30). It's server side parsing (those bastards) and it can't be removed. Is there some way to tell it to stop? The end line is USUALLY > or blank, BUT sometimes it's anything, the major difference is the tells extra lines will usually be at least 5 or more spaces to start (Depends on the person's name sending) and the other lines at most usually have 3 or 4 (hence 5 spaces then %s on the cond). So roughly the end line is any line that DOESN'T start with 5 spaces. It might be just a blank line, a > or anything else for that matter. If this is posted somewhere else still point me to it, I did try searching and I must just be using the wrong keywords. I used to think there was some Achea Channel capture that did almost exactly this with different syntaxes but same idea, but I couldn't find it.

Adept Joined: 04 May 2007 Posts: 292 Location: Boston

[editing out things here because I did not understand the question]

OK I think this is the solution, sorry the prompt is not reliable, in this link it says how to match everything but the lines with 5 spaces. I think I know that offhand but you will like this

http://www.regular-expressions.info/

no that's not right either, I give up

Posted: Sat Mar 15, 2008 6:44 am

Maybe something akin to this will do the trick. I tend to use two triggers for this, since you never really know the number of lines.

Posted: Sat Mar 15, 2008 8:06 am

need a space between pattern and value brackets on tellcapture

Posted: Sat Mar 15, 2008 5:24 pm

I hope you don't mind, I went back and fixed that space and your pattern. You don't need to begin or end a trigger with * ever.

Apprentice Joined: 29 Jul 2002 Posts: 105

I like it. I was using ^{ | |} but it was breaking a little and that was the condition and ... yeah it was missing occasional lines (I think empty lines). I like that but I don't QUITe get how the {^{^ }*} works. I looked and ^ means don't match... so don't match 5 spaces, then don't match ANYTHING else... wouldn't you want 5 spaces? It seems to work so far so I won't argue, just trying to learn how and why things work so I can use them if I ever need/want to later.

Apprentice Joined: 29 Jul 2002 Posts: 105

Okay it makes some more sense. As ^ is the start line character. I have a single problem and I am not quite sure how to make it work. Sometimes as I said it's a blank line. It's rare, but it does happen.
ALSO
when I get two things with you tell to start it, that are both one line, it fails. Is there a way to arrange the priority or somesuch to make it able to fire on itself twice if the state pushes it back?

Apprentice Joined: 29 Jul 2002 Posts: 105

What about making the extra tellcapture trigger... fire on the other version... So something like..

Posted: Sat Mar 15, 2008 7:32 pm

No worries. As I said, it was mostly at the top of my head.

Apprentice Joined: 29 Jul 2002 Posts: 105

Here's how I ended up. And yes I know it's not what I said, but I had multiple versions, one for channels, and one for tells, all had the same problem but luckily only channels had the able to follow each other problem.

Apprentice Joined: 29 Jul 2002 Posts: 105