Zugg Software :: View topic

Beginner Joined: 06 Nov 2006 Posts: 26

#TRIGGER {(x)(y)} {#PSUB "%2"}

Now, this trigger should essentially just remove x from the line and leave me with y (which it does do).

However, it is also causing the line it below to be appended to the end of the one being #PSUBed.

So if the MUD output:
xy
abc

I want:
y
abc

But I get:
yabc

With the trigger on.

Is this correct? If so, how do i put the new line back in? I tried %concating the #PSUB with a %{cr} but the result wasn't good (it appeared to hide the next line.

Or if this isnt correct.. then is it a bug?

Morgal

Posted: Wed Nov 08, 2006 6:10 pm

In CMUD, the " quotes are used for literal strings. Variables and functions (like %2) are NOT expanded within quotes. This was normally the rule in zMUD, but the %1..%99 were exceptions that broke the rules. This exception isn't allowed in CMUD.

Because the "" were a kludge in zMUD, you can mostly just remove them in CMUD. The following syntax is the correct way to do it in CMUD:

Beginner Joined: 06 Nov 2006 Posts: 26

Thanks Zugg,

Just letting you know that taking out/putting in the " " around %2 makes no difference to the way cMUD handles the trigger. So it appears the variables ARE being expanded. (Is this a bug? As you said they weren't expanded)

I know you are supposed to use start and end values for it, but, to quote your help file:
"If XStart is omitted, the beginning of the line is used. If XEnd is omitted, the end of the line is used."

So it is valid (although not intended).

Anyway, what I actually intended by making this topic appears to have got lost along the way. My point is.. that if #PSUB is used, and it isnt given a specific end, it eats the end of line characters.

This can be shown by

Posted: Thu Nov 09, 2006 5:21 pm

Thanks for the extra info. Yes, you are right about how it should work with the XStart and XEnd omitted, so the fact that it seems to eat the following lines is a bug.

I'll check the "%1". It isn't supposed to be working in CMUD, so this might be a bug too. There are some commands that actually treat their arguments as literal values and then parse them themselves, so maybe that's it. Or, maybe I forgot and added code to the parser to allow %1..%99 in quotes. It's been almost a year since I wrote the core parser for CMUD, and it's possible that I added something and forgot about it. Anyway, I'll check into it.

Beginner Joined: 06 Nov 2006 Posts: 26

Just to clarify, it doesnt eat the following lines, it just eats the end of line characters.

Morgal

Posted: Thu Nov 09, 2006 8:07 pm

Actually, when I tested your first example, it never displayed the "abc" on the following line. I did this: