using bash a 93x68 gnome terminal window will result in a corrupt display after pressing up-arrow to retrieve a long command line and then using left arrow (or ctrl-a) to move to the beginning of the command line.
What's your prompt string like?
Hm... can't reproduce this here. You aren't doing anything odd like putting the prompt in the titlebar, are you?
I've seen this since 5.2, maybe earlier. It's a major pain in the ... It happens with xterm too. It's been reported on the beta tester's mailing list several times. I most often see it when doing ^R to reverse search for a long command. Rather than properly wrapping the lines, the line display gets totally hosed. I just tried to give a sequence of commands which reproduces it consistently, but failed. I had two windows up (143x24), one exhibiting this hosed behavior, and a newly created identical one without problems. However, I finally noticed that in the hosed window, the COLUMNS env variable was still set to 80, whereas in the good window it was set to 143. Resizing the window made the problem go away. So, it seems like sometimes bash is missing the resize notification or getting it wrong or some such thing. Fiddling this some more I was able to recreate the symptoms: 1. start bash in an xterm (when in your home directory): xterm -geometry 80x24 -e bash & 2. Run less: less .bashrc 3. Resize the window to 149 columns. 4. exit less 5. echo $COLUMNS (should still be 80 instead of 149) 6. issue command: echo this is a test of the american broadcast system. If this were an actual emergency then this broadcast would not work. ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha (all on one line). 7. Do a reverse search for 'echo this is' ^Recho this is As the characters for the reverse search are entered, the screen update of the line gets seriously munged. It could be that the line length was always missed if a program was running when the window was resized (I recall something like this occurring in the past), but that bash/xterm interaction in the past might have been better when the line length was wrong.
This works fine for me here. Did you install a brand new 6.1 or is this a result of an upgrade? DId you install packages like ncurses that are not provided by Red Hat?