Discworld, triggers and column length

Hi there all. I have a problem with the discworld Mud and my triggers. I'm trying to get all the output sent to notepad rather than the main screen. typically the chat will have the word 'wispy voice' in it so i used that as the trigger. i.e. "*wispy voice*".
i have it set up to 'omit from output' and 'append to notepad'.
This all works fine, except that mushclient only has problems with lines longer than ther column length that has been negotiated between my terminal and the server. What happens then then is that up until the max column length (before text begins to wrap) it will append to notepad but after that mushclient prints the rest of the output back to the world window. geddit?
i get why this is happening. mushclient evaluates a line for any keywords/alphanums but it misses the end of long lines because they are automatically wrapped to the next line, so mushclient doesn't evaluate them. how do i prevent this, i.e. how do i tell mushclient to evaluate a long line altogether?

If the mud is asking Mushclient how many columns are there and setting its end to that, then there is probably nothing you can do, since mushclient isn't the one wrapping the line, the mud is. As far as Mushclient would be concerned, it has recieved multiple lines, not one single line that was being wrapped. If Mushclient is doing the wrapping and it is still treating such lines as seperate then imho that constitutes a bug, since frankly I don't care how the client wraps things, it should 'know' that everything being wrapped is on one line for purposes of omitting from output.

That said, the only way to do this for mutliple lines if the mud is doing the wrapping is to have one trigger start grabbing the content and activate a two others. One would be a 'capture everything' and the second would look for a terminating line and deactive itself and the capture trigger. The problem is figuring out this end event. If all communications ended in ", then you could just look for that, but most muds allow the person talking to leave off punctuation and don't add anything to the line they type, so you get things like:

Fred, in a wispy voice, tells you: I have to go

No period, nothing to distinguish the end of the line, etc. Unless the following lines are auto indented by the mud and you can use the fact that the next line that arrives "isn't" to turn off the capture, you are out of luck. There is no practical solution to this problem on probably 99% of muds. Imho, if they automatically added "" around all player communications or the like it would make our lives a whole heck of a lot easier. lol

thanks, i thought up a solution even as i was reading your post. i decided rather than to pay any attention to the probelm of columns i would use colour instead. in Discworld you can set chat to certain colours. i have set it to magenta (hideous but notepad doesn't display it ;P )and just used a wildcard to capture all magenta output and append it to notepad. sorted, 'cause whether or not there is a new line in a long sentence it's still gonna be magenta!
thanks very much. tata.

Very good. MUSHclient would work if it wrapped the output, so the MUD must be wrapping. You might be able to turn that wrapping off.