Two bugs in 4.1.1

I've ran into two bugs in Lyntin 4.1.1. Platform Win2k, Python 2.3.4. 
Using Tkui, but both can be reproduced in textui as well.

Starting with the one that seems to be quite simple:

The #snoop command appears broken. '#snoop <session> on/off' produces an 
error, stating that there is no method setSnoop defined in the Session 
class. This is indeed the case.

The second bug:

Lyntin seems to have trouble with long (_long_) lines. As a test case, I 
generated a plain ascii file with the character 'a' 10000 times. Lyntin 
chokes pretty badly as I try to view this file (more, cat, ... on my 
mud). After several seconds the file is printed and Lyntin resumes to 
normal speed. Prior to Lyntin printing the line, it slows down to crawl, 
not displaying anything from the mud and making typing on the input line 
nearly impossible.

Approximately same amount of data (10000 times 'a'), if split to 
separate lines, gets printed normally (no slowdown). I tested this by 
adding a '\n' between every 80 characters in the previously mentioned 
test file.

I realize that it is usually rare that a mud sends such a large chunk of 
text without newlines in it, but initially I found out about the problem 
in a real situation as I tried to check out a user's savefile on my mud. 
These files have a large mapping (LPC for associative array :) storing 
certain type of data, and this mapping, presented as a single line, was 
long enough to choke Lyntin.

A 10000 characters long line is somewhat excessive, 5000 characters is 
enough to be very noticeable, practically freezing the client for 
several seconds.

Tuomas


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click