Closed sorin-ionescu closed 12 years ago
[Extended winter vacation, and now slowly catching up. Sorry for the delay.]
Hmm, I can't replicate this.
I suspect your terminal uses an encoding that is incapable of handling ✗. I don't think it would be that hard to put a workaround in if that is the case, but it I'm not sure how to handle it. The possibilities are the standard str.encode
ones; ignore the unusable characters or replace them with ?
. Neither of which are particularly desirable, and both would need a pretty hefty warning mixed in if they're triggered.
I have tried it in both iTerm and Terminal, which both use UTF-8. It's not a terminal issue. It's definitely a unicode-related Python problem, which we will hopefully never see once the planet transitions to Python 3. I'll upgrade hubugs to HEAD. Perhaps, it has been fixed.
I've upgraded to HEAD. It still happens.
Are you using one of the hubugs dependencies argh, github2, html2text, Jinja2, markdown2, Pygments that is newer than what's available on PyPI?
Okay, I can produce a similar error by breaking my locale settings and now the traceback makes far more sense. While I wasn't receiving an error initially, I was still receiving garbled output :/
Can you try again with the commit I just pushed?
It now works. Thank you.
hubugs -p robbyrussell/oh-my-zsh show -f -p 627