Linebreaking not working about viper HOT 10 CLOSED

Yes I have the same problem. Frankly I don't know how to fix it tho.

from viper.

I think I found a solution. The bug is documented here: http://bugs.python.org/issue17337
There is a link to a possible fix: https://stackoverflow.com/questions/9468435/look-how-to-fix-column-calculation-in-python-readline-if-use-color-prompt

So, if in viper/common/colors.py the color is returned as:

return "\x01\x1b[%dm\x02%s\x01\x1b[0m\x02" % (color_code, text)

The linebreaking works. Unfortunately, if you output colors that way without using readline, it will print bogus chars. My quick and dirty fix was to add a default argument escape=False to the color functions and set this only to true when building the prompt. Its not really beautiful. Surely you can think of something better ;)

from viper.

Just changing the return line works for me. didnt set escape= anywhere. and have yet to see bogus chars.

Ubuntu 14.04 x64 server via putty0.63

Although Scrolling through the history now removes the prompt

from viper.

Please let me know which one is the best solution you guys encounter so that we can fix it.
If we need to tradeoff between things, we might even decide to get rid of the colors in the prompt (although that would be sad).

from viper.

Maybe the broken output happens only with zsh. I will test this and provide screenshots when I get around to it. Might take some days, though.

from viper.

No, happens with bash as well.

from viper.

Indeed it does.
Bogus chars with zsh:

And with bash:

My system is an up-to-data Arch Linux with Openbox. I also tested multiple terminal emulators, all have the same problem.

Note that there seem to be no problems with the conditional solution I proposed above, other than that it might not be the most elegant one.

from viper.

if it works commit :)

from viper.

I created a pull request: #129
It's my first, so bear with me if I did something wrong ;)

from viper.

think this can be closed now

from viper.