Bug with colored prompt

[bchretien]

Hi!

I had the need to disable the colored prompt because of the following bug: using ctrl + A to go to the beginning of the line "fails" when using a colored prompt. It instead goes to an offsetted position (probably because of the color escape codes) and modifying the line becomes quite tedious. Then scrolling up to the previous command and down again to get an empty prompt also leads to an offsetted prompt that can't be fully erased:

Sorry for the obfuscated description ;-) I don't know if this is easily soluble, but the least I could do was report it.

[gdbinit]

Ah I know this one, never bothered too much with it. Moving to the local is a good idea.

[bchretien]

Related issues with bash/zsh:

• http://unix.stackexchange.com/questions/90772/first-characters-of-the-command-repeated-in-the-display-when-completing
• https://bugs.launchpad.net/ubuntu/+source/bash/+bug/119938

[frameloss]

Just came across this project and I really like what you have done, thanks for all the effort.

Here is info on how to fix the readline problem: http://www.dirac.org/linux/gdb/03-Initialization,_Listing,_And_Running.php#acaveatforcoloredgdbprompts

Mine is set to the following and readline works correctly (changed to yellow prompt, but otherwise illustrates the point.)
set prompt \001\033[33m\002gdb$ \001\033[0m\002

[RadioheadFonts]

An easier fix for this is simply adding 0; before the red color code.

set prompt \033[0;31mgdb$ \033[0m