long commands overwrite themselves

r.j.hall · n00b Joined: 06 Feb 2003 Posts: 53 Location: London

why is it that sometimes in my konsole if I am typing a long command it doesn't linefeed correctly, instead it seems to start overwriting itself and moves the whole lot up one line also overwriting the previous line. If I try and go back in the command and edit it, even stranger things start happening.

Is this a common problem?
Is there an easy solution to prevent it?

Thanks
Rich
_________________
--- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
You've read it.
You can't unread it!
--- --- --- --- --- --- --- --- --- --- --- --- --- --- ---

Tyir · Posted: Wed Jun 23, 2004 5:05 pm Post subject:

no idea how to prevent it, but i get it sometimes too!
_________________
There are two things I have learnt in life:
1. Don't reveal everything you know.

Useful Idiot · Guru Joined: 30 Aug 2002 Posts: 329 Location: Finland

Does this happen after you have resized konsole window? If it does add

Zyne · Guru Joined: 08 Jun 2004 Posts: 334

lol... I'm getting this too from time to time... Really weird.
it happens mostly if it's the last line you're writing. The text above doesn't seem to move up anymore... :/

I'm gonna try Useful Idiot's solution, and see what that gives me.
btw this happens to me in aterm, and the only solution is to close aterm, and start a new console.

sapphirecat · Guru Joined: 15 Jan 2003 Posts: 376

I've seen this happen in screen+xterm, especially with less, in which case a ^A ^L restores it. (I can't remember offhand if any resizing was involved, though...) If you're not using screen, hitting ^L from the shell prompt may help, although it will clear the screen as well.
_________________
Former Gentoo user; switched to Kubuntu 7.04 when I got sick of waiting on gcc. Chance of thread necro if you reply now approaching 100%...

Slack006 · Posted: Sat Jun 26, 2004 7:12 pm Post subject:

I had this same thing happen to me... Are you using color codes in your prompt? That was my issue.

:oops:

I wish I could give you the exacts, but I am stuck at work and unable to get to my machine. The gist of it was I didn't properly escape my color codes. (Extra brackets needed, or a missing backslash or some such crap). Message me back if you don't get it figured out. To test, take the color codes out of your PS1 and see if the issue goes away. I'll post my shell color codes when I get home if you need them.

_________________
Slack

May the SOURCE be with you...

phranzee · Guru Joined: 22 Nov 2003 Posts: 397 Location: katowice/pl

every color declaration in your prompt should look like this:

Slack006 · Posted: Sat Jun 26, 2004 7:18 pm Post subject:

Exactly.

That's where I was screwing up. Basically, if you don't properly escape the code, then the shell doesn't know exactly how long your prompt is (chars), and thus doesn't know when to wrap...
_________________
Slack

May the SOURCE be with you...

InfinityX · Guru Joined: 31 Jan 2004 Posts: 385

So is there something wrong with this one?

Slack006 · Posted: Sat Jun 26, 2004 8:43 pm Post subject:

I don't see anything wrong with it... However, here's what I use in my .bashrc..

gnuageux · Veteran Joined: 17 Apr 2004 Posts: 1201

I like:

export PS1='\[\e[32m\]\u@\h \[\e[1;31m\]\w\[\e[1;34m\]\$\[\e[0m\] '
_________________
The realOTW: http://forums.realotw.org/index.php

Registered Linux user#364538

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

Erm... I don't get it. I'm a complete n00b with fixing bash. It always just worked before.

Can someone explain what it is I have to do? Do I have to edit some kind of configuration script for bash somewhere - and if so which one and how?

This is a deeply annoying problem, as bash is something I use pretty much all the time in Linux. It would be very tough to have to live without it.

GJ

sf_alpha · Posted: Sun Aug 08, 2004 10:57 pm Post subject:

It cause by curses based program terminate uncorrectly.

try

echo -n -e '\033c'

(Terminal Reset)

I think it not work all time but my Linux console.
_________________
Gentoo Mirrors in Thailand (and AP)
http://gentoo.in.th

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

No it didn't work for me. I'm embarrased to say I don't even quite understand what these guys are talking about. I wish someone would explain it to me.

GJ

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

Bump... Guys please be nice and explain how to do this.

Thanks....

GJ

conchyliferous · n00b Joined: 28 May 2005 Posts: 50 Location: Sweden

Got a problem with bash. It doesn't change line like it should. When the input fills up the terminal the first time and it should change line it doesn't. The input just starts to the left again and "eats up" that line. When it comes to the end of the terminal again it changes line like it should.

frostschutz · Advocate Joined: 22 Feb 2005 Posts: 2977 Location: Germany

Is this in an xterm, or text console?

In xterm, Bash sometimes assumes wrong window sizes and breaks too early / too late (happens when you resize/maximize your window while Bash is not currently active). Resizing the window again while in bash prompt fixes this problem.

Also, Bash may get flakey when you print binary data to stdout... in that case, 'clear' and 'reset' may fix the problem.

beatryder · Veteran Joined: 08 Apr 2005 Posts: 1138

can you post the out put of

fangorn · Veteran Joined: 31 Jul 2004 Posts: 1886

I know this behaviour from xterm. There exists a variable "XTerm*autoWrap: true" that does automatically use a new line at the end.

Edit:
should really answer directly, not after some minutes :roll:

_________________
Video Encoding scripts collection | Project page

conchyliferous · n00b Joined: 28 May 2005 Posts: 50 Location: Sweden

Sorry for the late reply.
I'm using urxvt and I know that resizing can mess things up sometimes but it ain't that easy this time I'm afraid.

My PS1 follows here:

tomk · Posted: Mon Feb 27, 2006 1:35 pm Post subject:

Merged from here.
_________________
Search | Read | Answer | Report | Strip