When I'm in Terminal and I type a long command or something, instead of the Terminal continuing the command onto the next line, it starts overwriting my username@host prompt. Does anyone know how to fix this?
MacBook Pro with Retina display, OS X Mountain Lion (10.8.4)
It must be something to do with the escaped color codes. Try using tput in the following way (this is approximately the colors you have in the above definition):
PS1="\[$(tput bold)\]\[$(tput setaf 5)\]malt@\[$(tput setaf 2)\]xxx: $ \[$(tput sgr0)\]"
It must be something to do with the escaped color codes. Try using tput in the following way (this is approximately the colors you have in the above definition):
PS1="\[$(tput bold)\]\[$(tput setaf 5)\]malt@\[$(tput setaf 2)\]xxx: $ \[$(tput sgr0)\]"
NOTE: What fixed your problem was putting any non-printing characters between \[ ... \] escaped square brackets. This is how you tell the promote NOT to count those characters so that it knows when to go to a newline, and not to count those characters when editing a command line.
The use of tput is fine, but your raw escape sequence would have also been fine, if you have wrapped it in \[ ... \]
PS1='\[\033[1;37\]malt@\[\033[1;32m\]xxx: \[\033[0;00m\]\$ '
What's the specific line you added to the profile to add the colors? There may be a syntax issue somewhere.
Alternatively, if you think the syntax is ok, then you can always escape a return character when you get to the end of the window for a long command. To do this, at any point in the command string you can type a back-slash, and then press Enter to get to a new line and continue the command, such as the following to run the deeply buried "lsregister" command (you can copy these four lines and paste them in the Terminal, and the "lsregister" command will be run):
/System/Library/Frameworks/CoreSe\
rvices.framework/Versions/A/Framewo\
rks/LaunchServices.framework/Versio\
ns/A/Support/lsregisterThanks man!
Here's the specific PS1 variable I set:
PS1='\033[1;37malt@\033[1;32mxxx: \033[0;00m\$ '
echo $BASH_VERSIONIf the version is 4 or higher, the behavior is normal.
Yeah. I've added color to the prompt. So like \033[1;34malt@xxx\033[0;00m"
While the colors look great and works well, the long commands stuff don't go to the next line. Is there any way to fix this while still having colors within the prompt?
Yep, that's exactly correct man. I just also fixed another issue too by doing this.
The other issue that I had is that if I tried to scroll to a previous command and hit Home to go to the beginning of that command, it'd jump only to like half the command... It'd be pretty screwed up.
So thank you for helping me fix two of the problems I've been experiencing 🙂
For the colors, the "setaf" value is the following:
1 -- Red
2 -- Green
3 -- Yellow
4 -- Blue
5 -- Magenta
6 -- Cyan
7 -- White
Sweet! This fixed it for me! I truly appreciate it!!
@Linc Davis, my bash version os 3.2.48(1)-release
Does it happen in all user accounts? You may have altered your bash shell profiles in some way. To check this, run the following commands, and then post the results of each here (the results should open in a TextEdit window):
cat ~/.bash_profile | open -fecat ~/.bashrc | open -fecat /etc/profile | open -feLong commands in bash terminal overwrites my prompt, instead of new line