Zugg Software :: View topic

Novice Joined: 08 Mar 2001 Posts: 44

I'm going to try to be as detailed as possible:

When I upgraded to 6.62 I immediately noticed a problem with lines ending only in a newline character( 'n' ). It seems to lag the screen for a second untill it is done receiving lines ended by n only, causing a sort of flashing on the screen(or if on a slower computer, it displays each line as its received, but takes forever to go through all the lines).

Something else that is happening with this, is if I have split screen on, the n isn't interpreted correctly, meaning it doesn't go down to the next line like it is supposed to.

I've tested this on two different muds, one with MCCP and one with out. Same effects from both.

I really hope this isn't a feature now, because it is rather annoying when tons of spam come through and I can't read it unless I scroll back, which makes any further data all come in on one line.

I guess this is just speculation about it only happening when a line is ended with n only, but since I've tested it by coding certain things on a MUD to end with n, nr and r, and it only happened with n by itself, I'm pretty sure that is the problem.

And I've tried about every configuration in the preferences, and still nothing helps(and changing the carriage control to CR instead of LF makes double spaces between each line).

So if this is a bug, please squash it. And if it is something that I can do, someone PLEASE TELL ME! :)

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

Try e-mailing Zugg with this information to see what he has to say.

Kjata

Posted: Wed Jun 04, 2003 6:35 pm

Here is the reply I sent to the email that you sent:
-----
Two comments on this. First, if you can log onto the MUD and create a trace file using the command:

#DEBUG test.txt trace.txt

and then do whatever command on the MUD causes the bad output to display. Then send me both the test.txt and trace.txt files as email attachments so that I can replay them here. Then I can see exactly what the MUD is sending to see what the problem might be.

The second comment is that according to the Telnet protocol specification, each line from the MUD should be terminated by a CR/LF combination (rn). If you are just sending a n without sending the r first, then your MUD is not following the telnet spec that is supposed to be used by MUDs. In this situation, the client is going to interpret n as a single linefeed character and will move down a line without changing the column position. In recent versions of zMUD, the operation of a single n was fixed to allow zMUD to work with unix editors such as vi and emacs. In older versions, zMUD treated n as a rn combination, but that is no longer the case and may cause problems with zMUD on non-compliant MUDs.

So, if you are in control over your MUD code, you should change your single n terminations to be the correct rn instead.

Posted: Wed Jun 04, 2003 6:36 pm

Here is the reply I sent to the email that you sent:
-----
Two comments on this. First, if you can log onto the MUD and create a trace file using the command:

#DEBUG test.txt trace.txt

and then do whatever command on the MUD causes the bad output to display. Then send me both the test.txt and trace.txt files as email attachments so that I can replay them here. Then I can see exactly what the MUD is sending to see what the problem might be.

The second comment is that according to the Telnet protocol specification, each line from the MUD should be terminated by a CR/LF combination (rn). If you are just sending a n without sending the r first, then your MUD is not following the telnet spec that is supposed to be used by MUDs. In this situation, the client is going to interpret n as a single linefeed character and will move down a line without changing the column position. In recent versions of zMUD, the operation of a single n was fixed to allow zMUD to work with unix editors such as vi and emacs. In older versions, zMUD treated n as a rn combination, but that is no longer the case and may cause problems with zMUD on non-compliant MUDs.

So, if you are in control over your MUD code, you should change your single n terminations to be the correct rn instead.