Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 59356 - new bash-3.0 broke my 2-line prompt
Summary: new bash-3.0 broke my 2-line prompt
Status: RESOLVED DUPLICATE of bug 36393
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-04 01:49 UTC by Sebastian
Modified: 2005-07-17 13:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian 2004-08-04 01:49:46 UTC
i use this prompt since bash 2.05x :
PS1="\[\033[1;34m\][ \w ]\[\033[0m\]\n[\[\033[31m\]\u@\h \[\033[0m\]\t]\[\033[31m\]=>\[\033[0m\]"

and and i see on my console/terminal:
[ /tmp ]
[heinz@h0me 12:14:56]=>
(with bash 3.0, too)

BUT:
the newline function (\n) is strange since bash 3.0

example:
[ /tmp ]
[heinz@h0me 12:14:56]=>eeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeee
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

and it should be:
[ /tmp ]
[heinz@h0me 12:14:56]=>eeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeee

and i can't edit the line, because the cursor has a hiccup and didn't reach the first line.

playing around with PS1="\u \w \n" shows strange effects, too.
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

and it should be:
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee


Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Ciaran McCreesh 2004-08-04 02:16:23 UTC

*** This bug has been marked as a duplicate of 36393 ***
Comment 2 Sebastian 2004-08-04 02:28:11 UTC
problem is with bash-3.0-r4 still there !
Comment 3 Sebastian 2004-08-04 10:29:11 UTC

*** This bug has been marked as a duplicate of 36393 ***