Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 9 Dec 1998 08:43:28 +1030
From:      Greg Lehey <grog@lemis.com>
To:        bjc23@hermes.cam.ac.uk, "Jason C. Wells" <jcwells@u.washington.edu>
Cc:        questions@FreeBSD.ORG
Subject:   Re: Bash bug when typing long lines?
Message-ID:  <19981209084328.M12688@freebie.lemis.com>
In-Reply-To: <Pine.BSF.4.05.9812082050570.17032-100000@bjc23.trin.cam.ac.uk>; from Ben J. Cohen on Tue, Dec 08, 1998 at 08:56:15PM %2B0000
References:  <Pine.BSF.4.05.9812081227550.909-100000@s8-37-26.student.washington.edu> <Pine.BSF.4.05.9812082050570.17032-100000@bjc23.trin.cam.ac.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday,  8 December 1998 at 20:56:15 +0000, Ben J. Cohen wrote:
>>> 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.

Jason is describing one way that bash can be set up.  It sounds like
he misunderstood your description.

> Is it likely that I have set something up wrong?

Yes.  I've been using bash, xterm and BSD together for nearly 9 years,
and it has never done this to me.

> 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)?

I'd guess that it's the termcap definition, but that's a guess.  I've
put two files on ftp://ftp.lemis.com/pub:

  bash is the version of bash I'm using (3.0).
  TERM is a script which sets the termcap to what I'm using

Try bash first; if that doesn't work, try
  
  . TERM

It's important to use ., because you want to have the effects in the
shell you're running.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981209084328.M12688>