From owner-freebsd-questions Tue Dec 8 14:09:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18771 for freebsd-questions-outgoing; Tue, 8 Dec 1998 14:09:58 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from www.crb-web.com (ns1.crb-web.com [209.70.120.131]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA18766 for ; Tue, 8 Dec 1998 14:09:57 -0800 (PST) (envelope-from wayne@crb.crb-web.com) Received: (qmail 12030 invoked by uid 1001); 8 Dec 1998 22:54:32 -0000 Date: Tue, 8 Dec 1998 17:54:32 -0500 (EST) From: Wayne Cuddy Reply-To: wayne@crb-web.com To: "Ben J. Cohen" cc: "Jason C. Wells" , questions@FreeBSD.ORG Subject: Re: Bash bug when typing long lines? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On some systems this will push a new line on others I have seen the behavior mentioned when it pushes the line to the left of the cursor. I suspect a terminal definition problem. On Tue, 8 Dec 1998, Ben J. Cohen wrote: > Date: Tue, 8 Dec 1998 20:56:15 +0000 (GMT) > From: "Ben J. Cohen" > To: "Jason C. Wells" > Cc: questions@FreeBSD.ORG > Subject: Re: Bash bug when typing long lines? > > >>There seems to be a glitch in bash when typing lines longer than one > >>screen-width. > >>When you do this, the cursor wraps back to the start of the line, but does > >>not go down a line, so you overtype the beginning of the same line. > > > >I don't think it overwrites the line. It just shifts the stuff you have > >written to the left so you can read the tail end. Use the left arrow to > >back up and see if this is the case. > > No, this doesn't seem to be the case; in fact, since if you do that the > line that was overwritten appears on the preivous line up, it seems to > confirm that this is wrong. > > Is it likely that I have set something up wrong? > > I think it was the default configuration, though. > > Note that this still happens when I run screen under xterm with bash; does > this suggest that the problem is with xterm (or my xterm definition)? > > Incidentally, I am running FreeBSD 3.0-RELEASE and I had the same problem > with the May(ish) 3.0 SNAPshot. I installed Debian Linux (briefly!) on > Friday and it didn't have the same problem. > > Thanks, > > Ben. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message