Terminal annoyances (broken linewrapping)

hw-tph

After a fairly recent reinstall of laptop, going back to Gentoo, I have encountered a weird problem. As many experience, the default shopt setting in Gentoo for checkwinsize is to have it disabled, and that's fine with me. I have always had shopt -s checkwinsize in my ~/.bashrc (and my ~/.bash_profile sourcing my .bashrc) to turn it on in order to avoid typing over what I have already typed.

Now, after my recent reinstall of Gentoo, I can't seem to enable it again. It appears to be enabled, but it doesn't work - not in aterm, not in my framebuffer console:

hw-tph · Posted: Tue May 25, 2004 6:10 pm Post subject:

Almost a month since my original post, and still no solution. The funny thing this also appears on my main desktop now, which did not have this problem before. I've tried it all, with checkwinsize, without...always the same problem. In aterm, console, xterm...the same all over.

Håkan

ArsDangor · Guru Joined: 20 May 2003 Posts: 477

I've had the same problem with Konsole.

In my case, the problem was that it set the variable TERM to xterm, when it was actually Konsole.
All I did was

John5788 · Posted: Sun Jun 13, 2004 1:17 am Post subject:

hey this happens to me too on Eterm.

hw-tph · Posted: Mon Jun 14, 2004 1:39 pm Post subject:

I have no problem with setting the correct terminal type and whatever terminal type I use doesn't seem to matter. It appears on linux, xterm and aterm/rxvt all the same.

I have noticed now that it only appears when I have su'd to root. Very weird, especially since "shopt -s checkwinsize" is specified in both my own and root's ~/.bashrc (and ~/.bashrc is sourced from ~/.bash_profile in both cases so it is always set).

Håkan

solka · Posted: Mon Jun 14, 2004 2:05 pm Post subject:

I have the same problem since I've installed linux and I can't get it working...I hope that a fix exists

_________________
"The only reason of the man's sadness
is that he can't stay peacefully in his room."

Blaise Pascal

Ian Goldby · Posted: Mon Jun 14, 2004 2:23 pm Post subject:

Try setting your prompt to something very simple. Sometimes incorrect control codes in your prompt (e.g. for colours) can cause exactly this behaviour.

solka · Posted: Mon Jun 14, 2004 2:25 pm Post subject:

I solved my problem.
According to this post, but also to bash manpage, what causes wrong line wrapping are escaping characters in PS1/PS2. After fixing it I had correct line wrapping.
_________________
"The only reason of the man's sadness
is that he can't stay peacefully in his room."

Blaise Pascal

MagnusBerg · Posted: Mon Jun 14, 2004 3:33 pm Post subject:

Look in you ~/.inputrc or etc/inputrc if you have a line with

hw-tph · Posted: Mon Jun 14, 2004 10:42 pm Post subject:

Ian - bang right on the money! Thanks a lot. I had missed one escape sequence in root's PS1 line. Now, I'll take my stuff and go hide in shame somewhere for a while.

Håkan

c07 · Veteran Joined: 25 Oct 2002 Posts: 1091

I had the same problem on a newly installed system. Bash ignored the horizontal-scroll-mode setting and treated it as always on (it has to if it doesn't know how to place the cursor a line up).

Re-emerging bash solved the problem. Seems it relied on some package (most likely readline) not present on the system at the time of the initial installation. Works well now, even with a colored PS1 and with all TERMs I use.

humbletech99 · Veteran Joined: 26 May 2005 Posts: 1229 Location: London

sorry for reopening this thread but my post was blocked by a moderator and I was directed here.

I've got this same problem and I've tried commenting out everything in all the files that bash reads at startup, I eventually moved all the files away so that I just got a bare bash-3.1$ prompt but the problem with the x terminals remains.

Does anybody else have any advice on how to fix this?