Prompt command display error about bash-it

[meirish]

I've got the same issue on Lion w/ Terminal.app.

[farneman]

I've fooled around in the scripts and narrowed down that the issue seems to be with the preexec.bash script. If I remove the calls to the precmd and preexec functions then the "\e]0;some command" bit goes away. Both those functions seem to only return true. I'm not very familiar with shell scripting and the bash prompt to know what that's doing.

The top of preexec.bash mentions that it was tested to work on OS X 10.4. Since it runs fine on my 10.5 machine, my guess is that something was updated in 10.6 causing the script to no longer work properly in post 10.5 versions of OS X.

[farneman]

After posting my previous comment I've further narrowed the issue down to the set_xterm_title function in the xterm.plugins.bash script. Disabling the xterm plugin fixed the issue for me. Cnn you check if you have the xterm plugin enabled @meirish ?

[meirish]

I was playing around and just decide to upgrade my version of bash (the one that ships with OS X is pretty old). I did it via home brew: brew install bash and then followed the instructions here: http://concisionandconcinnity.blogspot.com/2009/03/upgrade-bash-to-40-in-mac-os-x.html to register the new version and set it as the default for my user. After I did that, the double errors went away.

[tswicegood]

Out of curiousity, does #106 help with this? Not sure if they're related, but they might be?

[farneman]

@tswicegood I've pulled in the changes from #106, but I'm still seeing the same issue. Perhaps the xterm plugin still needs some work.

[hansstimer]

Upgrading to bash 4.2 solved the prompt problem for me. I followed meirish's directions above.

[kyanny]

$ rm ~/.bash_it/plugins/enabled/xterm.plugins.bash

It works for me. Broken prompt no longer shown. OSX Lion (10.7.3) and Bash 3.2.48(1)-release (x86_64-apple-darwin11)

[tswicegood]

I just ran into this on a fresh install of bash-it, but couldn't track down the culprit. I'll try nixing the xterm plugin and see if that fixes it. Odd part was that on another fresh install it worked. I think there's a difference in the default .bash_profile and my .bash_profile that changed it up. Wasn't TERM -- I checked that.

[farneman]

I've confirmed that removing/unenabling the xterm plugin fixes the issue for me.

[tswicegood]

Ok, so the fix here is to not use the xterm plugin. I've renamed it to _xterm and modified the installation script to ignore it. That should fix it for most people while not entirely removing the functionality.