So, I was wondering whether it'd be possible for you to treat IAC GA/EOR as a newline for the purposes of triggers and everything else, but not -display- it as a newline? So if something was recieved like:
<stuff> IAC GA <more stuff, maybe with newlines>
a trigger such as ^<stuff>$ would match correctly, and all other handling would be similar, except that on the screen, IAC GA is not rendered as a newline. Is this possible? Thanks -Tsunami
Worstje probably just wants a set of triggers that fire on the prompt, but don't change how the output looks to the user. I know on the mud that I play on, a few people would get annoyed at the extra line. Then again, other people don't like that I don't toss in blank lines after plugin output, so I have a flag they can set for the extra lines. Most are rather indifferent though.
My understanding is that that is the way GA/EOR is supposed to be handled. Ie, that it signifies the end of the line, which the client can handle as needed, but should not be displayed as a newline character. I could be wrong of course.
I think that the go-ahead command was to have a meaning similar to the "over" convention in radio. My understanding from reading a few websites is that the lines were half-duplex in that only one person could be sending data at a time. Therefore, when the server was done printing its output and wanted the user to do something, it would send a go-ahead to indicate that it was done printing for now.
So it is not necessarily an end-of-line command, rather, it is a prompt for input of sorts.
So I suppose that for the purposes of handling triggers, it might make sense to treat it as an end-of-line, because it marks a clear termination of a "logical line" sent by the server.
Nonetheless this seems relatively easy to implement in a packet analyzing plugin, no?
Uhm, I never wanted anything. I can do everything I want with the IAC EOR/GA option. I was merely replying to Tsunami. :)
If you want to gag the extra line that follows it, you can just trigger the prompt (which can be triggered once you have it on since the setting translates it to a complete line that MUSHclient can process), which turns on a group that triggers an empty line first and then any line, essentially making it possible to gag the superfluous line without affecting other empty lines that you may wish to keep.
That is in fact exactly what I have done. The issue (and it's not a very big one) is that sometimes the prompt is followed by an intentional newline, not one produced as a result of GA/EOR, and which thus should not be gagged. Still, as I mentionned it really doesn't affect me at all, it's just a stylistic issue.