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 ➜ General ➜ Omit from log sometimes lets carriage returns slip through

Omit from log sometimes lets carriage returns slip through

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


Posted by Boxknife   (19 posts)  Bio
Date Thu 27 Nov 2008 01:02 AM (UTC)
Message
Sometimes carriage returns get through after I write a trigger to gag a line of output from the mud, but I'm not sure why. Most of the time, they don't.

Could it be something I'm doing differently in the trigger pattern?
Top

Posted by Worstje   Netherlands  (899 posts)  Bio
Date Reply #1 on Thu 27 Nov 2008 01:30 AM (UTC)
Message
It is quite a vague question, and I don't have a definite answer. Nick probably does, but I'll give it a shot anyhow.

First of all, you have no other conflicting triggers that do get it logged?

Second, is the newline per chance arriving in another packet, or is an extra newline somehow arriving? Perhaps MUSHclient somehow gets confused, I don't know.

It would probably be helpful if you could give the trigger in question, and some output with the Debug Packets function in the Edit menu of when it does happen, and does not happen. This would give us more information as to what could be causing your problem.

Top

Posted by Nick Gammon   Australia  (23,140 posts)  Bio   Forum Administrator
Date Reply #2 on Thu 27 Nov 2008 05:38 AM (UTC)
Message
I have seen this a bit when playing with Aardwolf triggers. Basically the reason it appears to let extra lines through is that the lines are actually there - because the MUD sends a newline when it thinks you just had a prompt. One workaround is to make a trigger that omits multiple blank lines - I think there have been a couple of posts recently about that.

- 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.


10,932 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.