|
Atreides096 Beginner
Joined: 26 Apr 2004 Posts: 15 Location: USA
|
Posted: Mon Apr 26, 2004 12:31 pm
Need help improving a trigger |
I'm playing a MUD with too many channels to keep tabs of, and was trying to split these into windows using the #capture command. I am wondering if #capture is not the best way to go about it however, and was hoping someone might be able to help me refine the trigger:
#TRIGGER {(Group)} {#cap Group} "Captures" {case|verbatim}
Very simple trigger, and I have a couple of problems with it:
1) The format I want would be:
#TRIGGER {^(Group) %w: '*' } {#cap Group} "Captures" {case|verbatim}
But (I think because I had to use verbatim to get around the () in the trigger), I cannot get it to recognize anything beyind (Group).. this causes the obvious problem of capturing way too many things.
The second issue I have is that I sometimes see channels linked after my prompt, like:
<HP: 2140/2140, MN: 1766/1766 MV: 1521/1521, XP: 1232tnl QT:3, AL: 1000> (Group) Atreides: 'test'
So if I anchor the trigger with ^ I am missing many matching patterns.
If anyone could advise me, I'd appreciate it. |
|
|
|
Danlo Magician
Joined: 28 Nov 2003 Posts: 313 Location: Australia
|
Posted: Mon Apr 26, 2004 12:54 pm |
Try this:
#trigger {~(Group~) (%w): '(*)'} {#win Group ~(Group~) %
1: '%2'} "Captures"
To stop zmud parsing the parentheses and force it to match them, the quote character had to be used: ~ |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Mon Apr 26, 2004 6:24 pm |
To capture channels which occur on the same line with your prompt, don't use the ^ anchor.
Alternatively, use a second trigger with the prompt pattern preceding the channel pattern. |
|
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|