From owner-freebsd-questions Wed Sep 20 7:33:19 2000 Delivered-To: freebsd-questions@freebsd.org Received: from epicsol.org (epicsol.org [209.100.173.7]) by hub.freebsd.org (Postfix) with ESMTP id 612E137B423 for ; Wed, 20 Sep 2000 07:33:17 -0700 (PDT) Received: (from jnelson@localhost) by epicsol.org (8.9.3/8.9.3) id JAA16796; Wed, 20 Sep 2000 09:33:16 -0500 (CDT) (envelope-from jnelson) Date: Wed, 20 Sep 2000 09:33:16 -0500 (CDT) From: Jeremy Nelson Message-Id: <200009201433.JAA16796@epicsol.org> To: freebsd-questions@freebsd.org Subject: Re: Problems with screen/ircII In-Reply-To: <20000920080617.A96980@draenor.org> Organization: Damage, org. Cc: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> On Tue, 19 Sep 2000, Daan Franke wrote: >>> I use screen + aterm + BitchX and that fucks my screen up, but screen in >>> native console mode + BX gave a normal image. While BitchX + aterm is >>> normal and the old screen + aterm + BX was also normal >On Tue, Sep 19, 2000 at 11:56:27PM +0200, Morten A. Middelthon wrote: >> The problem only seems to occur when logging in via an xterm, I tried >> logging in from SecureCRT in Windows and ircII seemed to behave fine >> inside screen. Perhaps the term-type is set to something strange when >> logging in from an xterm? I can't check this now as I don't have any boxes >> at home with X running (no Geforce2 support in XFree..), but I'll try >> tomorrow when I get to work. In article <20000920080617.A96980@draenor.org> it was said >I can also only replicate this problem in X. If I use the console, I >have no problem with anything in screen. I've played around with the >term variable in xterm, and no matter what I set it to, I have problems. >:( For what it is worth, I am not seeing this behavior with screen-3.9.8 via xterm -- however, the first thing I do on a freebsd system is replace freebsd's ncurses distribution with an authentic ncurses distribution so that I can get terminfo support. Is there anyone else out there who uses terminfo that hasn't seen this problem? Perhaps it is termcap related. I use TERM=xterm1. Jeremy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message