Register forum user name Search FAQ

Gammon Forum

Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the password reset link.

Due to spam on this forum, all posts now need moderator approval.

 Entire forum ➜ MUSHclient ➜ Tips and tricks ➜ Multi-line trigger woes

Multi-line trigger woes

It is now over 60 days since the last post. This thread is closed.     Refresh page


Posted by Heliomance   (5 posts)  Bio
Date Thu 06 Sep 2007 04:57 PM (UTC)
Message
I want a trigger that will match on a certain line. Unfortunately, this line could be absolutely anything, there is no way to predict what form it will take. Fortunately, it is always immediately preceded and followed by ------------------------------------
I want a trigger which will look for the two ----------------------------- then send the middle line - the random one - to the script for parsing. After much trial and error, I have a trigger which looks like this:
^---------------------------------------------------------------------------$\n^ ((.)+)(?U)$\n^---------------------------------------------------------------------------$

which works, and sends the line to wildcards[0]. The trouble is, I haven't got the faintest idea why it works, especially as it doesn't work if you take the (?U) out. Can someone help me make a more sensible trigger, and explain to me how it works please?
Top

Posted by Nick Gammon   Australia  (23,173 posts)  Bio   Forum Administrator
Date Reply #1 on Thu 06 Sep 2007 10:59 PM (UTC)
Message
You can shorten it by using a "count" like this:


^-{75}$\n^ ((.)+)(?U)$\n^-{75}$


The (?U) sets the "ungreedy" option, which makes it match on the minimum it can rather than the maximum.

- Nick Gammon

www.gammon.com.au, www.mushclient.com
Top

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.


11,264 views.

It is now over 60 days since the last post. This thread is closed.     Refresh page

Go to topic:           Search the forum


[Go to top] top

Information and images on this site are licensed under the Creative Commons Attribution 3.0 Australia License unless stated otherwise.