> > It doesn't blow up on me when I run it and type /go 200. > Although it doesn't cause errors, it does truncate the number of printed > lines. 37/50 or 128/200
Right, it doesn't croak() or something. It doesn't print all the lines -- which is problematic enough -- and it causes serious prompt issues (at least on my terminal settings) for continued use of the client. When I run it, it usually stops about halfway across a line (usually the same one, but not always) and then draws my prompt there. It sends a \r and leaves my cursor at the start of the line (promptless). If I type something it draws the prompt correctly (but not until then) ... and it stays that way until I restart the client. Something is definitely goes wrong -- even if you don't see the full extent of the prompt redraw trouble, missing lines is enough of a problem. Where did they go? -Paul
